Subject | Re: [ib-support] Re: Error in interbase.log |
---|---|
Author | Jason Chapman (JAC2) |
Post date | 2002-04-10T14:15:36Z |
mana_s1965
Does this mean that you can run your production system happily using rc1 or
fb1 (except after 3 -4 hours fb1 slows to a stop).
chnage or that code change, but the first thing to do is try and identify
exactly what is causing the slowdown, so you need to build a test plan, you
need to simulate in test what your users are doing and see what gives.
In our systems we audit when users go from on customer record to another, so
we can emulate a days worth of browsing but building robot clients.
I would be looking at getting 80 DB connections in test on fresh databases
with each server and then go through some testing like.
Each of the 80 connection read data from the databases with increasing
complexity of query.
Repeat with some updates and inserts going on.
I haven't tested RC1 vs release.
Sorry if this seems common sense, it is just where I would start.
JAC.
> How many user ?Have you tried the rc1 engine with the DB that is slowing?
> about 60-80 users.When I reboot my server that can serve my client
> about 3-4 hours.
>
> The lastest Test
> I try to install firebird rc1(9 Apr,2002).It can serve all day (I don't
> adjust config or parameter and programming).
Does this mean that you can run your production system happily using rc1 or
fb1 (except after 3 -4 hours fb1 slows to a stop).
> I compare firebird rc1 with final release.It have different aboutI didn't develop any part of FB, so I couldn't say it could be this code
> connecting.
> 1. fb rc1 connect slower than fb 1.0.0
> 2. fb rc speed ok when have many concurrent users but fb 1.0.0
> not ok
chnage or that code change, but the first thing to do is try and identify
exactly what is causing the slowdown, so you need to build a test plan, you
need to simulate in test what your users are doing and see what gives.
In our systems we audit when users go from on customer record to another, so
we can emulate a days worth of browsing but building robot clients.
I would be looking at getting 80 DB connections in test on fresh databases
with each server and then go through some testing like.
Each of the 80 connection read data from the databases with increasing
complexity of query.
Repeat with some updates and inserts going on.
I haven't tested RC1 vs release.
Sorry if this seems common sense, it is just where I would start.
JAC.