Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Session database in memory, mirrored to another host for redundancy, and only events that need to be stored written to "slow" SSDs when I/O bandwidth permits.

I could bring my startup from 10 to 2 hosts and have better performance.



To be fair, that should be doable right now with DDR3. It's still much faster than an SSD.


I suppose that's true, thanks for putting that in perspective.

The real problem is that gobs of RAM isn't _cheap_. I wish that DDR4 would make DDR3 less expensive, but as manufacturers switch to making DDR4, I expect the price to rise.

edit: Which is to say, I'd be happy if it became possible in the near future to get laptops with 48GB of of DD3 and junky Dell rackmounts with 256GB of RAM for today's prices of 16/64GB respectively.


> Which is to say, I'd be happy if it became possible in the near future to get laptops with 48GB of of DD3

The reason laptops still come with just 4GB of RAM has little to do with the cost of RAM. Each gig you add reduces battery life significantly.


My last several laptops (System76) came with 16GB. Though I have never looked at the impact to battery...

I run multiple VMs on my machine continuously (a win7 VM and a couple other linux VMs). The machine has dual SSDs and it's super freaking fast.


There are also diminishing returns for the average user. My mother would notice an SSD, but probably not another 4 gigabytes of RAM. Her computer almost never hits the swap partition.


That's quite common. Redis etc.


redis is key/value, not meaning to be full normalized database


Redis has complex data structures, not just key/val. You can also run a SQL db in-memory anyway.


it's still k/v, it's just the values can be several different types of DS




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: