From: Jon A. <jon...@ne...> - 2010-08-05 15:54:39
|
Treebaseprod (on dev server) is 123 GB as compared to 180 GB for the production database on the main treebase.org website. I'm OK with testing the performance on treebaseprod as it would save us a day of restores and the size is still significant. I will need to point treebase-dev.nescent.org to that database should that be the way we want to go. Let me know. Thanks, Jon On Aug 5, 2010, at 10:02 AM, William Piel wrote: > > On Aug 5, 2010, at 8:41 PM, Hilmar Lapp wrote: > >> I would expect the primary source of >> performance degradation, if there is one, to come from updating large >> indexes, which, if done record by record that is inserted > > Okay. On treebasedb-dev there is a database called treebaseprod, which might be closest in size to the current production database. If we have a build that points to that, perhaps that would be our best performance comparison? Or alternatively, perhaps delete treebaseprod and replace it with a duplicate of the current database -- that would provide the closest size for performance comparison. > > bp > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Treebase-devel mailing list > Tre...@li... > https://lists.sourceforge.net/lists/listinfo/treebase-devel ------------------------------------------------------- Jon Auman Systems Administrator National Evolutionary Synthesis Center Duke University http:www.nescent.org jon...@ne... ------------------------------------------------------ |