Archive for the ‘General’ Category
Then please contact us: i n f o (at) o u r d e l t a (dot) o r g
What are the requirements? Having a server with HTTP access and no hassles with low traffic limits. At this stage you’ll need about 5GB disk space, and you’ll use rsync to sync from the master servers (we’ll provide you with a script to help with that). Thanks!
With the new releases the traffic is up (not surprising) and while our existing mirrors appear to be doing ok so far, it’ll be good to have more available before we run into capacity or speed problems. We also haven’t yet split for geographic location, that too becomes a possibility with more mirrors.
Some of you may have run the mysql-test-run tool which is the MySQL test suite. But did you know there are actually multiple suites? If you just run the tool, you don’t get everything!
Check out the mysql-test/suites subdirectory. That’s all the stuff you don’t get when just running the tool normally. If you take a peek at the Makefiles, you will find a target test-bt (build team) which shows the extra calls and parameters for the additional suites.
OurDelta has had some interesting cases where a build that’s otherwise ok would fail when users tried the test suite on their installation. We reckon such a test should definitely pass, and thus we had some more homework to do. So now OurDelta builds with as many tests as exist enabled, on all platforms and architectures. Slow yes, but that’s not an argument to not test something, right? Failing tests are often indicative of other issues, so at the very least they merit some attention.
For instance… we found that on some platforms, the default distro packages are actually broken in fairly interesting ways. The testsuite in particular falls victim to this, making one wonder whether the distros actually test what they build, and which tests they do.
General idea… base: Delta symbol (with thicker line on right hand side – a delta it’s not a regular triangle), plus one or more of the following:
- something depicting deltas: incremental small changes;
- something depicting a river delta: where streams come together before flowing into ocean;
- something depicting community: people working together, participating, communicating.
If you can draw even a little bit, rough scribbles are most welcome! We have a good artist who can turn that into magic. And, you don’t have to go with the above… come up with something else suitable!
See also https://bugs.launchpad.net/ourdelta/+bug/284161 where we’re tracking this; you will find other suggestions from people, including ideas that have been dismissed for visual or other reasons.
This poll was posted last week on Arjen’s blog and is still open for a few more days to receive your vote. The comments on the original post contain some interesting considerations either way, and many in fact non-technical. Anyway, please add your vote, and optionally your thoughts to the comment thread!
The setup on Launchpad is better organised (Launchpad rocks!), and we already have the first feedback in the form of bugreports – mainly on the packaging and repo information. That’s excellent! Thanks Vladimir Cherednichenko, Steve Walsh, and Peter Lieverdink! Peter actually deserves a special mention as he has put in a lot of work on the debian packaging.
Also, because sometimes instant banter is useful, there’s now a #ourdelta channel on Freenode. Naturally, real discussion should just happen on the ourdelta-developers team and list. It’s really easy to join.
Antony Curtis did just that (join) and already put one of his many patches in: this one fixes issues which occur while a thread is running ::open() or ::create() on any storage engine. Typically the LOCK_open mutex is held and it could block other threads from doing work. While it needs some work, it might be a worthwhile modification. Mutex contention is an important issue for scaling, and this one is at a fairly high level.