Remove 2003 Remove Benchmarking Remove Network Remove Scalability
article thumbnail

Why Tcl is 700% faster than Python for database benchmarking

HammerDB

Python is a popular programming language, especially for beginners, and consequently we see it occurring in places where it just shouldn’t be used, such as database benchmarking. We use stored procedures because, as the introductory post shows, using single SQL statements turns our database benchmark into a network test).

article thumbnail

Supercomputing Predictions: Custom CPUs, CXL3.0, and Petalith Architectures

Adrian Cockcroft

Here’s some predictions I’m making: Jack Dongarra’s efforts to highlight the low efficiency of the HPCG benchmark as an issue will influence the next generation of supercomputer architectures to optimize for sparse matrix computations. I presented a keynote for Sun at Supercomputing 2003 in Phoenix Arizona and included the slide shown below.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

What Adrian Did Next?—?Part 2?—?Sun Microsystems

Adrian Cockcroft

The early days at Sun Cambridge were special, I absorbed a lot about networking and the technical side of the role from my fellow systems engineer Martin Baines, and we were driving all over the region in cool company cars (I had a Citroen BX 16V) selling a really hot product.

Tuning 52
article thumbnail

HammerDB Concepts and Architecture

HammerDB

This article Threads Done Right… With Tcl gives an excellent overview of these capabilities and it should be clear that to build a scalable benchmarking tool this thread performance and scalability is key. You can download and compile TCL/TK 8.6 HammerDB CLI v3.1 HammerDB CLI v3.1

article thumbnail

SQL Server I/O Basics Chapter #2

SQL Server According to Bob

url=/library/en-us/fileio/fs/sparse_files.asp ) ​​ on the ​​ Microsoft Developer Network ​​ (MSDN). ​​ For example, ​​ the I/O speed of a snapshot database could limit certain query scalabilities. The following are a few reasons this error may be encountered.

Servers 40