MK saves up your added rows in ram until you call commit(), so you could commit more often. also, MK memory-maps the storage file, so it becomes part of your virtual address space. it then pages it in, rather than doing file i/o. it only gets those parts of the file that it is using, which in general means whole columns as you access them. blocked views can reduce the size of the data it pages in, by breaking up the columns tranparently to your code.
--- "Nemec, Bernhard" <[EMAIL PROTECTED]> wrote: > Hello, > > I am evaluating Metakit and have looked at the memory usage under linux. I > wrote a test program in C++ that adds batches of 5000 rows to a view and > commits after each batch, repeating this every few seconds. > > I noticed that the RAM usage of my test program grows linearly as more rows > are added. > What can I do to limit the RAM usage of such a program? > > Thanks, > Bernhard > _____________________________________________ > Metakit mailing list - [EMAIL PROTECTED] > http://www.equi4.com/mailman/listinfo/metakit __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ _____________________________________________ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
