For some reason, this Rudy Park cartoon really resonates with me.
I think it was a post by Robert Scoble that put me onto this, but gada.be.The site goes away and searches a number of other search engines to give you some top responses. Quite interesting…try running these and check the results:
It’s unfortunate that there’s the disparity between the Martin C Brown and Martin MC Brown; that change was one I made last year when I started blogging more regularly because most people know me as simply MC. At least though there’s a link.
Traditionally, high performance computing was carried out by specialized hardware and software working together to produce a highly optimized environment. Grids are beginning to change that, by removing the need for the specialized elements while enabling the spreading of the work across a wider range of hardware, software, and networks. A new article takes a closer look at the two solutions, and how they are converging.From the article introduction:
Parallel computing is a methodology for designing applications designed to work within large parallel computing environments. In a grid system, the execution of an operation or equation is geared toward providing a structure for executing tasks in parallel, where the order in which the work units are executed and received is not sequential and not reliant on previous code iterations. While, overall, the models of these two systems — parallel computing and grids — are converging, the traditional programming models of these two systems remain different. In this article, we will look at parallel computing, grids, and their convergence.
The next article in the System Administrators Toolkit series, this time on monitoring disk space and disk usage by users, is available at IBM developerWorks. This one focuses on finding out your disk storage, where it is being used, finding out who is using it, and, when necessary, controlling the usage through the quota system. From the developerWorks preview:
Look at methods for determining disk usage across multiple UNIX systems and how to create a simple warning system to alert you of potential problems. Keeping an eye on your file systems and ensuring they don’t fill up is a trivial, but vital process in the day-to-day management of your UNIX systems. In this article, you’ll look at methods for keeping an eye on disk space, discovering which files, users, or applications are using up the most space, and how to make use of quotas and other solutions to find the information you need.
One of my first major tasks at MySQL has just been completed – a major rewrite of the Connector/ODBC (C/ODBC) documentation. There were three major focuses for the rewrite:
- Bring the documentation up to date. We had a mix of information on the latest release (currently 3.51, but 5.0 is currently in development), but many of the sections didn’t reflect that new version. There is also new information on how to install the driver on Mac OS X.
- Restructure the information. This is something I’m doing across the board on the Connectors docs, as I try to re-organize them all into a more coherent, and compatible, structure. For example, I’ve collated all of the tips about using C/ODBC with different applications into their own section, organized by application. I’ve also extended the information; for example we now have a step by step guide to importing data from MySQL into Microsoft Word and Excel through Microsoft Query.
- Setting up the document so that I can more easily add and extend the information in there with tips from the community, bug fixes, and of course new releases.
I’ll now be continuing the work with the other Connectors, like Connector/J and Connector/NET.