On Thu, Dec 12, 2019 at 7:05 PM Kyle Stanley <aeros167@gmail.com> wrote:
Antoine Pitrou wrote:
1M concurrent database transactions? Does that sound reasonable at all? Your database administrator probably won't like you.
I agree that 1M concurrent transactions would not be reasonable for the vast majority of database configurations, I didn't mean to specifically imply that 1M would be something reasonable today. That's why I said "a large number of concurrent transactions" instead of specifically saying "1M concurrent transactions". I honestly don't know if any databases are close to capable of handling that many transactions at once, at least not at the present time.
I have personally worked on a database back end that was processing ~800k transactions per second, about 10 years ago. It was highly-specialised, ran on Big Iron, and was implemented in C/C++ (mostly), FORTRAN, and IIRC a smidgin of assembler. So those numbers may not be currently realistic for Python, or for general purpose RDBMSs, but they are not completely ridiculous. Cheers, Duane. -- "I never could learn to drink that blood and call it wine" - Bob Dylan