September 24, 2007 at 3:52 pm
I need to know what the current transactional record is per minute for SQL Server. Doesn't matter what the hardware or data model is or anything, just the most transactions that SQL Server has ever ran through in one minute. The other information; however, would be really appreciated as well.
Thanks,
Lezza
September 25, 2007 at 1:45 am
September 26, 2007 at 8:28 am
1,231,433 transactions per minute steady state on an almost 2 year old submission to tpc.org. I will venture a guess that that is fast enough for just about any production need in existance. What I find amazing is that for a total system cost (including clients) of $63K you can have a sql server system that will provide 69.5K transactions per minute. That ROCKS!!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
September 27, 2007 at 2:39 pm
Impressive information ... I have never pushed SQL Server to that etent.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
September 27, 2007 at 3:47 pm
Heck, I have only had a few situations in the last 15 years where sql server needed to process over 100K trans per minute, and that was usually for limited periods of time! 1M thingamabobbies per minute is a LOT of activity! 🙂
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
September 28, 2007 at 2:54 am
we're not mixing minutes and seconds here are we? I've been running systems which do over 350 transactions/sec for many years, I know that doesn't get near the tpc benchmark of cource. I'm not sure about the price thing though - suppose it depends but at around £14k per processor for enterprise ( 28k per proc in funny money ) not too sure how that figure is extracted. $41k doesn't buy much tin and storage, let alone clients!
I did some basic tests not so long ago which did 1.5k transactions/second over a sustained period. It's usually the disk subsystem which limits this speed btw.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
September 28, 2007 at 12:34 pm
totally agree with Colin, in those heavy OLTP system the dough is on the IO subsystem 😀
* Noel
September 28, 2007 at 1:49 pm
We ran into issues at JD Edwards with overload on our intranet. It wasn't that complex, but the CMS was issuing over 12k transactions/sec on the system, a plain old 4x4 and things slowed down.
Definitely IO counts, but application design can be huge as well.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply