News for hackers. Stuff that matters.

LinuxJedi

Re:The Australian Commodore 64 on Tuesday August 23, 2022 @02:25AM (#32561124)
Ah! Thank you, I was unsure if the C64C hit Australian shores. That definitely helps, I'll tweak my post accordingly.
Re:The Australian Commodore 64 on Tuesday August 23, 2022 @02:23AM (#32561109)
It is an original C64 but a company in Australian made an after market case for it to make it look more like the C64C without having to buy an entirely new computer.
Re:The Australian Commodore 64 on Tuesday August 23, 2022 @02:18AM (#32561065)
Sorry, I forgot that doesn't translate well outside the UK. It is a literal box for putting your bread in to keep it fresh and is a similar shape to the original C64. So the original C64 is nicked-named the "bread-bin" in the UK.
Re:The Australian Commodore 64 on Tuesday August 23, 2022 @02:16AM (#32561049)
Yea, I was erring on the side of that being OK. U27 was also a suspect so I tried that first. Update here: https://linuxjedi.co.uk/2022/08/23/australian-commodore-64-m...
Oh, I forgot we run DBT2 too
There are plans to bring back at least stored procs very soon. But to do them properly and as a plugin type (so if you don't need them they aren't there)
The link you supplied is the current effort to port phpMyAdmin. I'm not aware of any other similar projects right now. It would be really good to have such a thing though.
With InnoDB I believe that it stores the smaller int types as 4 byte anyway. But I am not an expert on this particular section code.
Drizzle7 is the GA release of Drizzle
We do plan to work on things like Rabbit and Tungsten replicators soon. In the mean time we recommend the native solution which is similar to MySQL's master/slave but uses the GBP messages stored in an InnoDB table.
We use SQLBench, Sysbench (I believe both are pretty standardized) and drizzleslap. I'll ask others in the team about the one you linked to, looks interesting.
I have a lot of respect for MariaDB, but they are aiming to be a drop-in replacement for MySQL. Drizzle is not a drop-in replacement and intentionally broke some compatibility to reach it's goals.
Faster is relative, Drizzle uses InnoDB as a storage engine and I suspect Postgres and Drizzle/InnoDB have optimizations for different workloads.

I would love to see benchmarks of things like OLTP workloads though.

Unfortunately we don't have any yet, although there are libdrizzle vs. libmysqlclient benchmarks floating around.

We don't benchmark against MySQL ourselves because we can very easily bias it in our favour. We would love to see other people benchmarking.

We do, however, benchmark every build against ourselves using several different suites as can be seen at:

https://launchpad.net/~drizzle-benchmark

A good point, quite a few people are using the libdrizzle client library bundled with Drizzle. It is a high-performance BSD licensed library that can speak the MySQL protocol.
Thanks for pointing that out :) The final part will be up tomorrow outlining the future plans for Drizzle.
beyond blogs (my wordpress blog included), forums and mail servers I don't believe it is used in a production environment yet. But Rackspace intends to use it in production environments.

We believe it is stable enough (hence the GA) our testing and regression suites are very comprehensive.