Hi Namshin, Marek, is there a way we can incorporate a measurement of memory usage into the megatests? This is a critical measure of performance, and we need an immediate warning if changes introduced to master break proper cache freeing. At this point, it'll be a pain in the ass trying to track down when cache clearing was broken, if it is now broken as Namshin says.
-- Chris On Jul 12, 2009, at 9:36 PM, Namshin Kim wrote: > Oops. annotation_hg18_megatest.py uses 48% memory when saving > results, too. Collection version didn't use that much memory, thus > we may need to re-organize a little bit. > > 2. SQLTableClustered clear_cache isn't working. The biggest megatest > is SNP annotation and retrieving megatest in > annotation_hg18_megatest.py. When building AnnotationDB, it uses 45% > memory (about 2GB). I thought we had solved this cache problem? > Collection version does not show this problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
