[V4RB] Open Delay

[Ruslan Zasukhin]

On 19/11/07 10:03 AM, "Schiller, Carsten" <c.schiller at peptidomics.com>
wrote:

> 
>> From: Ruslan Zasukhin [mailto:sunshine at public.kherson.ua]
>> 
>> On 16/11/07 5:06 PM, "Schiller, Carsten"
>> <c.schiller at peptidomics.com> wrote:
>> 
>>> I just tested a ~200 MB Database (3 tables, 40 fields, no indexes)
>>> took about 40 seconds just to execute the open function.
>> You can hear 
>>> a lot of memory swapping to the disk and if you open it a
>> second time 
>>> it opens almost immediately (until the computer is
>> rebooted). I think
>>> this is XP specific and no issue on the Macs.
>> 
>> Please do 
>> 
>>     SqlDump Structure only
>> 
>> This will produce 3 CREATE TABLE commands, and show them to us.
> 
> Here we are:
> 
> CREATE TABLE "fingerprint" (
> "diagnose" STRING (255)  NOT NULL,
> "path" STRING (255)  NOT NULL,
> "comment" STRING (255)  NOT NULL,
> "date" DATE  NOT NULL,
> "operator" STRING (255)  NOT NULL,
> "speccount" LONG  NOT NULL,
> "project" STRING (255)  NOT NULL,
> "stadium" LONG  NOT NULL,
> "instrument" STRING (255)  NOT NULL,
> "methode" STRING (255)  NOT NULL,
> "specimen" STRING (255)  NOT NULL,
> "specimen_source" STRING (255)  NOT NULL,
> "experiment" STRING (255)  NOT NULL,
> "patient" STRING (255)  NOT NULL,
> "picture" PICTURE (1024) ,
> "format" LONG  NOT NULL,
> "resolution" DOUBLE  NOT NULL,
> "align_MZ_ID" LONG  NOT NULL,
> "align_MZ_GUID" STRING (255)  NOT NULL);
> 
> CREATE TABLE "spectrum" (
> "Fingerprint_ptr" ULONG  NOT NULL INDEXED,
> "spectrum_data_X" BLOB (1024) ,
> "spectrum_path" STRING (255)  NOT NULL,
> "fraction_nr" LONG  NOT NULL,
> "scale" FLOAT  NOT NULL,
> "points" LONG  NOT NULL,
> "spectrum_data_Y" BLOB (1024) ,
> "spectrum_log" TEXT (1024) ,
> "offset" DOUBLE  NOT NULL,
> "outlier" LONG  NOT NULL);
> 
> CREATE TABLE "masslist" (
> "Spectrum_ptr" ULONG  NOT NULL INDEXED,
> "peak_xcoor" DOUBLE  NOT NULL,
> "peak_ycoor" DOUBLE  NOT NULL,
> "peak_intensity" DOUBLE  NOT NULL,
> "peak_width" DOUBLE  NOT NULL,
> "peak_area" DOUBLE  NOT NULL,
> "peak_quality" DOUBLE  NOT NULL,
> "peak_s2n" DOUBLE  NOT NULL);


Hmm, so tables do not have many fields!

Please try compress your db at best compression.
    RAR or ZIP7

And see its size. Let me know.
I'd like test it here.



-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]