does, however, like M4 still have the strange behaviour to be slower on
PreparedStatements. When swithing from server side prepared statements,
to Java emulated prepared statements, the performance goes to the same
level as simple batched statements, while Java wise, the emulated
version is much more computational extensive.
I'm under the impression that for update queries we have around the
absolute minimum of data sent over at this moment, hence the 'gap' we
have with MySQL must be in the engine and/or the driver. For the latter
I will have to investigate where shortcuts can be made, or inefficient
structures are being used (such as very frequent Map lookups with few
entries).
This benchmark only tests update queries (inserts, updates, deletes),
hence there is a need to revive a select based benchmark, or create one
to get an idea how we perform in other use cases. A conclusion from the
latest improvements is that searching for newlines appears to be
expensive in both Java as well as C. (Smack tests showed a 10x
speedup).
Future improvements on these responses from the server that are a
tabular result can be:
- change header format for easier parsing (I don't expect much from
this)
- replace newlines by integer lengths to avoid string scanning
- make parsing of tabular results easier/less expensive by avoiding
string escaping
The MonetDB team at MonetDB BV is pleased to announce a feature release
of the MonetDB JDBC driver (monetdb-jdbc-3.2.jre8.jar) and JdbcClient
CLI program (jdbcclient.jre8.jar).
The new release adds the capability to use the SQL:
COPY ... INTO ... ON CLIENT
statements via Java from the client side. This allows users and
programmers to use the much faster COPY statements to load large data
sets into MonetDB from a local client side CSV file or stream.
The JDBC MonetConnection API has been extended with methods to register
and use Upload and Download Handlers to stream the data from the Java
client application to the server and/or from the server to the Java
client. See <https://www.monetdb.org/downloads/Java/onclient.txt> for
details.
The new functionality has also been added to the JdbcClient CLI program,
so you can now also use COPY ... INTO ... ON CLIENT statements from this
CLI program, provided you have started it with a --csvdir argument. The
CSV data files may also be gzip compressed (file name ends with: .gz).
Besides this new functionality we also improved both the JDBC driver and
JdbcClient to work optimal with the new MonetDB Jan2022 server release.
For a list of all changes please read:
<https://www.monetdb.org/downloads/Java/ChangeLog>.
We recommend all users of MonetDB JDBC driver and/or JdbcClient program
to upgrade to this new release. Especially if you use the new MonetDB
Jan2022 server release, you should use the new jar files. The download
location is as usual: <https://www.monetdb.org/downloads/Java/>.
For information and tips on using the MonetDB JDBC driver, read:
<https://www.monetdb.org/downloads/Java/release.txt>.
Reminder: as of release monetdb-jdbc-3.0.jre8.jar the MonetDB JDBC
Driver class name has been changed to: org.monetdb.jdbc.MonetDriver
It used to be nl.cwi.monetdb.jdbc.MonetDriver which is marked as
deprecated. Please use the new driver class name asap in your
configuration files/scripts and/or Java code.
The old driver class name is currently still included in the jdbc jar
file but only to ease the transition for existing deployments. The old
driver class will be removed in a future release of the MonetDB JDBC driver.
