There can be many items in a grid. Do you have 1000s of projects ?  I so so, you could always filter them by date (year), or something like  that.

 

Thousands of  items loaded all at once means that the grid will take longer to load, and if you hoist some items (ctrl+h) and come back to those many thousands (displayed all at once), or if you need to refresh the grid,  it will  be slower than a "smaller" grid. But apart from that, it doesn't change much : once items are loaded, other operations aren't affected... as far as I can tell.

 

As an example, a  grid with 6 columns, and 5600  items will load in about 20s. But once it's loaded, it's business as usual. Most grids here load between 3 and 10s

 

Factors that will affect a grid's loading/refresh time :

- number of columns (but I have many grids with more than 50 columns and it's manageable)

- filter complexity (but you should generally be fine, even if you're a bit special, like me**)

- number of items in the  grid  (...)

- size of DB (after 7 years of pretty heavy usage, mine is about 450mb and performance is fine)

 

Factors that will affect other operations (item creation, moving item, etc.): field functions, auto-assign equations, inheritance (to be used very carfuly).

 

** with common filters looking like : Iditem in (27787,24154, 225196) or ((task)  And (focusdate is null) and (((due-now<=1 or due is null) and (followupdate-now<=0 or followupdate is null))   AND  (check is null and àClasser is null and keephidden is null))) | check is null

 

-------------------------------------------------------

Sony Vaio S Series 13 (SVS131E21L)

Ram:8gb, CPU: Intel i5-3230M, 2.6ghz

(Just for the record : refreshing a grid with 1000 items and 7 columns takes 2s or less here)

 

-------------------------------------------------------

Sony Vaio S Series 13 (SVS131E21L)

Ram:8gb, CPU: Intel i5-3230M, 2.6ghz