Run stadistic for database
- Look for index in de big tables. Look for Depth 2. In this case up Page
size one step, and run database statistical.
- Look memory at each step
Good luck
Germán
El Viernes, 12 de septiembre, 2014 15:37:38, Alexey Kovyazin a...@ib-aid.com
[firebird-support]
Run stadistic for database
- Look for index in de big tables. Look for Depth 2. In this case
up Page size one step, and run database statistical.
2 is quite conservative these days with the available hardware
resources and even with a 16K page size you may reach that threshold
with indexes
Hi Russel,
Good starting point could be our optimized configuration files:
http://ib-aid.com/en/optimized-firebird-configuration/
Regards,
Alexey Kovyazin
IBSurgeon
What type of access (read vs. write mix) are you expecting? Mainly write
What mix of small vs. large queries are you expecting?
We are having to gear up one of our web apps for a potential spike in access
next month and have been running some load testing. Overall it seems not to bad
but the database is a bit of a bottleneck or so it seems.
Without turning off forced rights what else should we look at? We have
We are having to gear up one of our web apps for a potential spike in access
next month and have been running some load testing. Overall it seems not
to bad but the database is a bit of a bottleneck or so it seems.
Without turning off forced rights what else should we look at? We have
What type of access (read vs. write mix) are you expecting? Mainly write
What mix of small vs. large queries are you expecting? the queries are
based on single order ids (primary keys) and about 4 tables involved
How many simultaneous connections are you expecting? that's the big
question we are
