Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 23 total
Thread Speeding things up
Mon, Sep 17 2007 7:12 AMPermanent Link

"Overall, based on elapsed time, the SSD array performed the queries 276
times faster than the ATA array."
http://www.dbazine.com/oracle/or-articles/ault6/view?searchterm=SSD

It makes me wonder if this is a way to speed things up. A 32Gb SSD is
available from stock in the UK for 300 GBP (approx US$600). Since our app
copies all the databases to a temporary location, this may be worth
investigating.

/Matthew Jones/
Mon, Sep 17 2007 8:51 AMPermanent Link

Someone elsewhere has pointed out that the article is from 2005, but it is
probably still relevant. I'm going to look into using a RamDisk for a
test, which would be cheaper.

/Matthew Jones/
Mon, Sep 17 2007 11:07 AMPermanent Link

"Frans van Daalen"

"Matthew Jones" <matthew@matthewdelme-jones.delme.com> wrote in message
news:memo.20070917134712.2624G@nothanks.nothanks.co.uk...
> Someone elsewhere has pointed out that the article is from 2005, but it is
> probably still relevant. I'm going to look into using a RamDisk for a
> test, which would be cheaper.
>
> /Matthew Jones/

http://www.anandtech.com/storage/showdoc.aspx?i=3064

MTRON SSD 32GB: Wile E. Coyote or Road Runner?

Mon, Sep 17 2007 3:18 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frans,

<< MTRON SSD 32GB: Wile E. Coyote or Road Runner?  >>

Wow, very impressive.  Especially since 32GB is well within the range of
most smaller databases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Sep 18 2007 4:38 AMPermanent Link

"Frans van Daalen"

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:CB95EBDF-683A-421F-8D80-F2355FDFC8AC@news.elevatesoft.com...
> Frans,
>
> << MTRON SSD 32GB: Wile E. Coyote or Road Runner?  >>
>
> Wow, very impressive.  Especially since 32GB is well within the range of
> most smaller databases.
>
Yes, it's on my list Smile

Shame that they did not have a db test.

HP (Alienware) created a laptop with dual-ssd 64gb in raid0 !

Tue, Sep 18 2007 8:45 AMPermanent Link

=?iso-8859-1?Q?Thomas_Eg_J=F8rgensen?=
"Frans van Daalen" <Account@is.invalid> skrev i en meddelelse
news:F04BBDBB-06E5-4F2A-94AE-7D1A166D174F@news.elevatesoft.com...
>> << MTRON SSD 32GB: Wile E. Coyote or Road Runner?  >>
>>
>> Wow, very impressive.  Especially since 32GB is well within the range
>> of most smaller databases.
>>
> Yes, it's on my list Smile
>
> Shame that they did not have a db test.
>

I'm going to order one of these(maybe the 2,5" depending on
deliverytime)
http://www.king-cart.com/cgi-bin/cart.cgi?store=dvnation&product_name=16GB+3.5+SATA+100MB/s+SSD&exact_match=exact

The combination of 0,1ms seektime and read/write speeds of
80MByte/100MByte per second seems quite niceSmile

....the main purpose is to do some DB testing(BTrieve, MSSQL and DBISAM
v3)...

I will report back when the disk arrive... Smile

/*Thomas
Tue, Sep 18 2007 11:22 AMPermanent Link

> I will report back when the disk arrive... Smile

Please do!

/Matthew Jones/
Wed, Sep 26 2007 6:08 AMPermanent Link

Okay, sometimes good things happen when your mind can have time to think.
I haven't managed to get around to buying an SSD drive to experiment with
yet. But I had on my todo list getting a RAM drive to experiment with
first. Then in a discussion about this, someone said "pity we can't hold
the whole database in memory", and I went "D'oh!".

So, the situation is that I have a set of tables and queries that
currently point to local tables. There may be more than one set of these
in threads, each with their own session. What would I need to do to make
these use a single memory table for the big write, and then at the end
have the tables "dumped" to disk? I'm hoping that the index writing in
particular would be much faster in memory.

Can I just set a "use memory" flag somewhere, or is there more to it.
Please point me at anything relevant. Many thanks.

/Matthew Jones/
Wed, Sep 26 2007 8:58 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Matthew


All you need to do to use a memory table (in DBISAM .. its a bit more complex in ElevateDB) is create a table in memory, set the TDBISAMTable's database to memory and go.

Best way to create the table is to use a TDBISAMQuery with its database set to memory.

I hope that's what you were asking. It would be good if you gave a few more details of what it is you're doing - this thread moved from SSD to how to "use memory" flag and I'm a bit lost Smiley

Roy Lambert
Wed, Sep 26 2007 12:43 PMPermanent Link

That does answer what I'm asking. I raised SSD because it looked like it
may give better database performance than disk. Then I realised that
"memory" would be faster still. No point spending on fancy SSD if the
basic thing does it better.

/Matthew Jones/
Page 1 of 3Next Page
Jump to Page:  1 2 3
Image