![]() Using an int for the index is the appropriate technical implementation until we need to scale beyond that. □□įor now we are targeting having 10k paying customers. To hire a PostgreSQL expert to do these kinds of micro-optimisations. If we reach the JIRA scale (complexity) it means we have more than enough cashflow □ Using an int for the index is more intuitive IMO. ![]() Going to avoid using Strings for the "rank" ( index) until we are forced to use them. This is a very fast update query even if there are hundreds of items in the listĪnd should not affect the performance/UX of our App for the foreseeable future. Even in a DB with 100 Million rows this will still happen in less than 50 ms because the update query will just be: This is a totally routine task in Postgres and Ecto. as noted, I don't expect that our DB will suffer too much from updating the rows for a list each time the ordering/priority is updated. Each work order has a status of ‘Unscheduled’ when imported into the db, and contains no appointment information, and therefore does not show on the calendar. A form application of work orders is linked to this gird. Thank you for sharing the link to the StackOverflow. I have a grid application that displays work orders. If we notice a significant performance bottleneck in this, we can target it for optimisation. It's not unheard of to have a 50 terabyte PostgreSQL database:Īnd there instances using Peta-Bytes. If the average size of an item is 1kb then it's 100 gigabytes for the whole DB. 100 items per list (though I think is quite a lot !) Then 100k people would have 100,000 x 1000 = 100,000,000 ( 100 Million) items in the DB. If each person has average 1k items spread over 10 lists i.e. The number of updates for each drag-and-drop event can potentially be the whole list.īut luckily we don't need to worry about that for the next year (at least!)īecause a decent capacity Postgres instance/cluster will handle 100k people using it without breaking a sweat. ![]() Right now we are 100% in the research & development phase.Īgreed. If you find a more efficient way of implementing this please share! Technical Implementation is 100% Flexible at this point!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |