05.01.2013 17:43, Ann Harrison wrote: > Err, no on three counts. The first is that there was no other activity on > the database > that demonstrated 1Tb of writes for a 55Gb database. The second is that even > if there > were conflicts, that sweep was done by a SuperServer configuration, so dirty > pages do not > go to disk when their lock is released. And finally, even if there were > conflicts and it > were a Classic installation, the only time large numbers of pages are forced > at once is on > commit.
It is not quite so. At first, if GC is in background mode, there are two parallel activity on database: GC cleaning up and sweep, reading page by page. Every time sweep is going to read next record, it requests read lock on page which forces GC to release exclusive lock of the page (if it has just cleaned a previous record). At second, TS didn't name architecture, so it is not necessary superserver. -- WBR, SD. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
