Subject | 2.0 SuperServer Vs Classic question |
---|---|
Author | fabianchocron |
Post date | 2006-11-24T05:19:38Z |
Hi Guys,
We have about 8 databases (1/2 Giga each) on a dual opteron 2.4
We have been running Firebird 1.5 in SS mode.
We are migrating to 2.0
If we swap to Classic 2.0, and let's say 5 users are running a heavy
query, and other 5 users are running updates, how is Firebird going to
respond in terms of response time, comparing with SS?
I guess my question could be simplified by asking:
How does Classic manages the "semaphores" when multiple updates are
running simultaneously?
From Experience, I would say Fb1.5 does it "sequentially", and 2.0 SS
seems to do it a bit better, like 90% processor for the heavy query,
and 10% for the restÂ… I wonder how would classic 2.0 manage a similar
situation.
We have about 8 databases (1/2 Giga each) on a dual opteron 2.4
We have been running Firebird 1.5 in SS mode.
We are migrating to 2.0
If we swap to Classic 2.0, and let's say 5 users are running a heavy
query, and other 5 users are running updates, how is Firebird going to
respond in terms of response time, comparing with SS?
I guess my question could be simplified by asking:
How does Classic manages the "semaphores" when multiple updates are
running simultaneously?
From Experience, I would say Fb1.5 does it "sequentially", and 2.0 SS
seems to do it a bit better, like 90% processor for the heavy query,
and 10% for the restÂ… I wonder how would classic 2.0 manage a similar
situation.