comment on

One of the things that make relational databases so efficient is that they are optimized to run on a spinning magnetic disk (like a hard drive). They take time to know just where the head is located physically over the platter and move it in the most efficient manner. This isn't to say that they won't run faster on a solid-state memory device, just that you throw out a lot of hard work if you do.

I don't think this is a reason not to move to a solid-state storage device, just something to keep in mind. If you can justify getting a TB memory array for your application, go ahead.

I don't know if there is any real optimization you can do for solid-state devices, or if those optimizations will even make for a significant speed advantage.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re: [OT] End of hard disks era, new ways of development by hardburn
in thread [OT] End of hard disks era, new ways of development by woolfy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks