• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Storage for Database  (Read 2301 times)

Karma: 0
Posts: 3

View Profile
« on: December 11, 2010, 06:02:09 AM »

I just bought a Guruplug server.
I'm quite happy with it.  Smiley
It makes more noise than a regular airport and that's an issue, but other than that i's a neat device.
Anyway, I'm looking into serving databases from it. MySQL and / or Postgres.
I was thinking about where to place the database files.
In my situation I have multiple options:
- Micro SD, but it's slow (6MB/s) and has about 10.000 writes.
  A database server writes a lot, and you don't want a corrupt storage location for database files.
- Internal storage, but it's only 512 MB for everything, leaving little space for database files.
  And same thing goed as for MicroSD, Slow and only 10.000 writes.
  And i'd rather waer out MicroSD card than internal Flash.
- NAS (NFS), but it is still quite slow and not recommended by PostGres. For MySQL soma are more positive than others.
 General opinion is don't use NFS for databases
- USB harddisk: I have one, but it's USB 2.0. Not so fast (faster than MicroSD and probably faster than NAS too, but neverthless).
  And on top of that, i'm already using it for other stuff.
- Buy a harddisk. USB 3.0 might do the trick, but eSATA is fasther. SSD might be a better option.
  However, than I would have two devices instead of one, using more energy, taking up more space and I have to buy something.  Cry

I don't do rocket science so I don't need the fastest sollution. But I'd like to choose the best option.
Has anyone of you any idea about what would be best te server my needs?
Do you have any experience with MicroSD, NFS, etc?
Please let me know if you do.

I'm looking forward to hearing from you.

Global Moderator
Sr. Member

Karma: 4
Posts: 273

View Profile
« Reply #1 on: December 11, 2010, 06:18:19 AM »

Personally, I'd think your primary consideration would be the size of the database, and a secondary one would be read-to-write ratio.

If the database is small enough to fit on an SDcard, I'd try that first.  Buy a fast one, and reads will probably be faster than a hard drive.  After all, you have no rotational delay to contend with.  And, they're building solid state hard drives now -- NAND memory packaged to look like a disk drive with a SATA interface -- so with active whitening, NAND has become quite robust with respect to tolerating write cycles.  If you need the space, or have an application with enough writes to make write timing an issue, choose a HD.  I would personally stay away from using the internal NAND for this task -- I don't think it is as fast, and it's not replaceable.

My two cents.


Karma: 0
Posts: 3

View Profile
« Reply #2 on: December 12, 2010, 06:06:13 AM »

Thanks for your info. It was very helpfull.
I checked some tech info and SD didn't seem so fast.
The only spec's I could find was MB/s and just as a comparisson:
- SD card / SSD: 6 MB/s
- NFS: 1 Gbit/sec??? (about 128 MB/sec)
- USB harddisk: 480 Mbit/s (about 60MB/s)
- ESATA: 3 Gbit/sec (about 375 MB/s)

But 'no spin time' could indeed be a big accelerator for small reads.
By the way, I forgot one option.
My NAS also support iSCSI.
I have a GB lan, so it could be quite fast.
I will check out SD card, NFS, iSCSI and USB harddisk somewhere next week.
I'll let you know some results.

Pages: [1]
Jump to: