Fabrik Limitations? Slow search with multiple users on 50k record table
Hi All,
Im working with a 50K+ row table/list (increasing by approx 500-1000 per week). With approx 30 elements per row.
The application, I wouldn't consider advanced, but in F3 and J!2.5.9 its seems much slower and cpu heavier than F2 and J1.5.
Table is currently 30mb.
Site is only 'main' one running on a quad core server (4 x 2.1ghz) with 4 gig ram.
When more than a couple of people start searching the list the mysql cpu usage rockets and simple searches (looking for an order ref or postcode for example) which would normally take max 2 seconds to return a result, can go up to 60 seconds +.
The list has only 10 elements as show in list, of which 6 are searchable.
Is there anything I can do to optomise this? Can I use just a search box on a form to query this list rather than loading the list first?
Thanks in advance.
Hi All,
Im working with a 50K+ row table/list (increasing by approx 500-1000 per week). With approx 30 elements per row.
The application, I wouldn't consider advanced, but in F3 and J!2.5.9 its seems much slower and cpu heavier than F2 and J1.5.
Table is currently 30mb.
Site is only 'main' one running on a quad core server (4 x 2.1ghz) with 4 gig ram.
When more than a couple of people start searching the list the mysql cpu usage rockets and simple searches (looking for an order ref or postcode for example) which would normally take max 2 seconds to return a result, can go up to 60 seconds +.
The list has only 10 elements as show in list, of which 6 are searchable.
Is there anything I can do to optomise this? Can I use just a search box on a form to query this list rather than loading the list first?
Thanks in advance.