Subject | Re[2]: [firebird-support] backup very slow and how often sweep a database ? |
---|---|
Author | Dmitry Kuzmenko |
Post date | 2011-12-22T09:28:50Z |
Hello, Vander!
Wednesday, December 21, 2011, 10:38:23 PM, you wrote:
VCS> Database header page information:
wow. what I can say.
You have 18.6 million transactions per day.
It is a huge number, but it's up to you,
because you know how many users and robots
working with this database.
For example, if there are 10 users working 24 hours,
then each user produces 21.5 transactions per second.
Even if there are 100 users working 24 hours,
it will be 2 transactions each second per user,
wich is still high, because I don't know human on earth
that can produce 2 transactions per second continuously
24 hours.
Robots? yes. Humans? No :-)
Since you already have Next transaction equal to 1 billion,
your database will stop functioning after next 54 days of
work, because Next transaction is signed int and can't handle
more than maxint. I think you already know this.
Next, your database have NO RESERVE flag turned on.
This is BAD, since you speaking about updates.
NO RESERVE is flag to compact data for read-only databases.
Using this flag for read-write databases causes more I/O
for updates and deletes, and performance of this database
will be worse than database without this flag.
--
Dmitry Kuzmenko, www.ib-aid.com
Wednesday, December 21, 2011, 10:38:23 PM, you wrote:
VCS> Database header page information:
wow. what I can say.
You have 18.6 million transactions per day.
It is a huge number, but it's up to you,
because you know how many users and robots
working with this database.
For example, if there are 10 users working 24 hours,
then each user produces 21.5 transactions per second.
Even if there are 100 users working 24 hours,
it will be 2 transactions each second per user,
wich is still high, because I don't know human on earth
that can produce 2 transactions per second continuously
24 hours.
Robots? yes. Humans? No :-)
Since you already have Next transaction equal to 1 billion,
your database will stop functioning after next 54 days of
work, because Next transaction is signed int and can't handle
more than maxint. I think you already know this.
Next, your database have NO RESERVE flag turned on.
This is BAD, since you speaking about updates.
NO RESERVE is flag to compact data for read-only databases.
Using this flag for read-write databases causes more I/O
for updates and deletes, and performance of this database
will be worse than database without this flag.
--
Dmitry Kuzmenko, www.ib-aid.com