> Thanks to everyone for their responses. So.. with all this being said,
> everyone is comfortable that the problem with not committing a
> transaction and waiting on garbage collection should max out the CPU
> and degrade performance indefinitely?

Yes, and beside that, are there any special reason for using the "no
reserve" attribute and running the database with forced writes off?

The first won't give you the possibility to have old record versions on
the same page as the data and with forced writes off, especially on
Windows, you might end up with a corrupt database, in case of a power
failure (without using a UPS) or an OS blue screen of death, ...


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com