Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

May 08 2012

finkregh
The MySQL server team have a bug fixing policy where a bug that has existed a long time has a lower priority 'because people know about them'. This is supposedly one of the reasons why the Bug#989 mentioned above has not been fixed.
Monty says: Oops, we did it again (MySQL 5.1 released as GA with crashing bugs)
Tags: mysql
finkregh
[...] We have changed the release model so that instead of focusing on quality and features our release is now defined by timeliness and features. Quality is not regarded to be that important. To quote Mårten Mickos: "MySQL 5.1 will be release as GA in or before December because I say so".[...]
Monty says: Oops, we did it again (MySQL 5.1 released as GA with crashing bugs)
Tags: mysql

September 17 2011

July 30 2011

November 04 2010

finkregh
[...]
MySQL ist nicht schön. Das muß es nicht, es soll nur den Job
erledigen und die Kasse voll machen. Und das tut es, zuverlässig,
wiederholbar und vor allen Dingen auf eine Weise, die man
normalbegabten Entwicklern in Kursen vermitteln kann. Alles ist allem
ist das in etwa das, was man von einem solchen Produkt erwarten
würde.

Die Zusammenfassung dieses recht langen Textes ist in etwa: Die reale
Welt ist nicht die Uni, und die Erfordernisse der realen Welt werden
für eine populäre Klasse von Anwendungen und Anforderungen  von MySQL
besser abgebildet als von jeder anderen Datenbank. Das MySQL dabei
gegen bestimmte traditionelle Lehren verstößt sorgt in gewissen
Kreisen für schlechte Presse, aber das ist den Leuten, die das machen
egal, solange die von ihnen erstellten Rechnungen korrekt genug sind
um akzeptiert zu werden und den Kühlschrank voll machen.
Re: Kann MySQL eigentlich irgendetwas, ... | Oracle erhöht Preise für MySQL | iX-Newsforen

September 29 2010

jcole’s weblog: Jeremy Cole’s take on life. » Blog Archive » The MySQL “swap insanity” problem and the effects of the NUMA architecture

When running MySQL on a large system (e.g., 64GB RAM and dual quad core CPUs) with a large InnoDB buffer pool (e.g., 48GB), over time, Linux decides to swap out potentially large amounts of memory, despite appearing1 to be under no real memory pressure. Monitoring reveals that at no time is the system in actual need of more memory than it has available; and memory isn’t leaking, mysqld‘s RSS is normal and stable.

Normally a tiny bit of swap usage could be OK (we’re really concerned about activity—swaps in and out), but in many cases, “real” useful memory is being swapped: primarily parts of InnoDB’s buffer pool. When it’s needed once again, a big performance hit is taken to swap it back in, causing random delays in random queries. This can cause overall unpredictable performance on production systems, and often once swapping starts, the system may enter a performance death-spiral.

July 16 2010

March 30 2010

July 26 2009

Choosing a non-relational database; why we migrated from MySQL to MongoDB « Boxed Ice Blog

Until recently, our server monitoring application, Server Density, was running using MySQL for the backend. Although we primarily provide it as a hosted service, it has been written to work as a standalone application for customers that wish to install on their own servers. This means each customer had their own MySQL database. We collect a lot of data – the monitoring agent reports back every 60 seconds and includes various statistics, of which the server snapshot has the most data (because it is collecting details on every running process). Over time, this results in millions of rows in the database, even for just 1 month of data, per server monitored.

July 07 2009

MySQL Multi-Master Replication Manager in Launchpad

MMM (MySQL Master-Master Replication Manager) is a set of flexible scripts to perform monitoring/failover and management of MySQL Master-Master replication configurations (with only one node writable at any time). The toolset also has the ability to read balance standard master/slave configurations with any number of slaves, so you can use it to move virtual IP addresses around a group of servers depending on whether they are behind in replication. The current version of this software is stable, but the authors would appreciate any comments, suggestions, bug reports about this version to make it even better. Current version 2.0 development is led by Pascal Hofmann. If you require support, advice or assistance with deployment, please contact Percona or Open Query.

April 21 2009

Sun, IBM, Cisco, Oracle - Die wunderbare Welt von Isotopp

Nun ist Sun gekauft worden, und zwar weder von IBM noch von Cisco, sondern von Oracle. Also fragen sich alle - was wird mit MySQL? Zunächst einmal gehören jetzt MySQL und InnoDB zur selben Firma. Oracle hat InnoDB seit dem Kauf recht gut gewartet und das kann jetzt ja nur noch besser werden. Wird Oracle MySQL absterben lassen und versuchen, seine eigenen Produkte in den Markt zu drücken? Nein. Wieso sollte Oracle das tun, und vor allen Dingen - welche eigenen Produkte denn?
Tags: MySQL sun oracle
Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!

Schweinderl