王 旭
2005-04-18 11:30:16 UTC
In maxdb help,there is a part of savepoint document:
As savepoints affect system performance, the database system does not
perform a new savepoint automatically at the end of this time interval. It
waits for 5,000 I/O operations and only then does it check how much time
has elapsed since the last savepoint. This means that the system does not
write a savepoint unless at least 5,000 I/O operations have taken place
since the last savepoint. With a lower number of I/O operations, more time
may elapse until the next savepoint.
And the "_Restart_time" is 600 sec!
Too long to active database writer and log writer.
In oracle,there is a concept named "checkpoint".I don't know whether
"chechpoint = savepoint"
thank!
_________________________________________________________________
与联机的朋友进行交流,请使用 MSN Messenger: http://messenger.msn.com/cn
As savepoints affect system performance, the database system does not
perform a new savepoint automatically at the end of this time interval. It
waits for 5,000 I/O operations and only then does it check how much time
has elapsed since the last savepoint. This means that the system does not
write a savepoint unless at least 5,000 I/O operations have taken place
since the last savepoint. With a lower number of I/O operations, more time
may elapse until the next savepoint.
And the "_Restart_time" is 600 sec!
Too long to active database writer and log writer.
In oracle,there is a concept named "checkpoint".I don't know whether
"chechpoint = savepoint"
thank!
_________________________________________________________________
与联机的朋友进行交流,请使用 MSN Messenger: http://messenger.msn.com/cn
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/maxdb?unsub=gcdm-***@m.gmane.org
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/maxdb?unsub=gcdm-***@m.gmane.org