30 ms·

Also, regarding "So yes, in this case it was possible to get multiple-minute load times in the worst cases. Why would anyone want to see many of these columns f

• gregmac 10y ago
  > most likely, because they either need to compute statistics or do an analysis that your app does not provide, or in order to make custom queries based on that output. Very well could be, and this is actually a very good example of why unbounded features like this are terrible to have. Using a main interactive view in the UI is not the way to achieve this. Data export, reporting systems, and/or APIs are the ways, and the big difference is performance is less of a factor. Over a second for a UI is a long time, but several seconds, or even several minutes, can be acceptable for data dumps/exports (that usually happen in the background, not user-interactive). One way to look at this, write a user story of the form "As a _____, I want to ____ so I can _____", and then use it to rationalize modifying a primary UI (in a performance negative way).. if it's truly compelling enough, then spend the time to make the UI work. In my experience, that type of thing is better left to background exports (where performance is not critical).