Memory consumption and big tables
Posted: Fri Oct 30, 2009 8:11 am
Hi!
I'm working on a big database (more than 12k records, more than 30 fields). Many functions of Xataface aren't working because Xataface try to load the entire table in memory to perform operations. I had to rewrite the cvs export function to export one row at time. Functions like update _set and copy_replace too are using a lot of memory when applied on the entire record set. I think some of the database access functions should be rewritten to work only on a few rows at time instead of working on the entire table.
Charles.
I'm working on a big database (more than 12k records, more than 30 fields). Many functions of Xataface aren't working because Xataface try to load the entire table in memory to perform operations. I had to rewrite the cvs export function to export one row at time. Functions like update _set and copy_replace too are using a lot of memory when applied on the entire record set. I think some of the database access functions should be rewritten to work only on a few rows at time instead of working on the entire table.
Charles.