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

Could you elaborate on SQL Server vs Redis claim? Or throw some references?

I am not doubting but just honestly asking. I've been discussing a possible Redis solution for complementing our current SQL Server.

Our problem isn't that big, we need to serve 10k req/sec of a simple query, can SQL Server do that? Isn't the connection pool the bottleneck to handle loads of this scale?



we need to serve 10k req/sec of a simple query, can SQL Server do that

Several years ago with SQL Server 2008 R2 I achieved 200,000+ simple queries per second (http://bit.ly/IlH2id -- this is not a regimented benchmark by any measure of the imagination, but is only saying "validate before assuming" because you might find your install performs far better than you anticipate) using the standard TDS query interface. This was on pretty beefy hardware, and is obviously enormously contingent on the data being in memory (which you can force with 2012), however it blew me away and completely undermined an initiative we had to implement AppFabric / Redis or other solutions.


> contingent on the data being in memory (which you can force with 2012)

What is the mechanism to do this in MSSQL 2012?


I haven't seen it on the new features of 2012, but I have seen it on some demos of 2014 Beta: http://stevenormrod.com/2013/09/an-overview-of-sql-server-20...


Whoops, I meant to say 2014.


I did not spot the mistake, simply assuming it was MSSQL version-after-2008.

Is Hekaton the feature you are referring to?




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

Search: