Developer.Com has selected MySQL Workbench as the best database tool of 2009!
Competing behind Workbench were:
- Altova DatabaseSpy® 2008
- LINQ (Microsoft® .NET Language Integrated Query)
- SQL Server® 2008 Reporting Services
- Oracle SQL Developer
Developer.Com has selected MySQL Workbench as the best database tool of 2009!
Competing behind Workbench were:
Developer.Com has selected MySQL Workbench as the best database tool of 2009!
Competing behind Workbench were:
Just today I got yet another email asking me why we do not rewrite PHP to get rid of all the cruft and past mistakes. These kinds of emails obviously have become more frequent since the namespace backslash decision. First up I wonder why people send such emails to me? After all I have only very rudimentary knowledge of C, let alone all the PHP specific infrastructure (macros etc.). So I am probably the person with the least ability to make something like that happen or even judge its feasibility among all of "PHP core" folks. But still since the question is often enough posed to me, I guess its more efficient if I reply to it in an easily linkable location. So the gist of my answer is: I would welcome a serious effort to rewrite PHP from scratch, but I do not think it should be done by PHP.net
Let me start with a disclaimer: Of course PHP is not without error. Far from it. …
[Read more]
You probably know that mysql -h host_or_ip
can
connect you to a remote host.
But did you know that you can change the host you are connected
to from within mysql
?
The undocumented (as far as I can tell, in the MySQL manual and
in the “help” on the mysql command line) CONNECT
statement can help.
(more…)
Lots of news…
We will be giving a Webinar on Waffle Grid on Febuarary 17th , if you want to know more you can find more details here … Also as mentioned previously We will also be talking about Waffle Grid at the 2009 MySQL User conference. So if your interested in learning more about Waffle Grid sign up and stop by.
I am also going to be giving a session at the MySQL User Unconference entitled “Learning from others’ MySQL Performance Mistakes” … it should be good fun, stop by and say hi.
I …
[Read more]In our environment we use Apache everywhere. It's PHP integration has so far proven superiour. Now we're dealing with higher loads and we've hit some limitations.
One of the problems we had, is Apache's heaviness. Our apache2 worker processes eat up around 20 Megabytes of memory, and with 3 GB of memory will bring us up to a setting of around 150 MaxClients. Rasmus seems to think that's a pretty high setting, but based off the easy calculation (memory available for apache / size of an apache process) it works out for us.
Effectively this means we can serve approximately this much parallel request on this machine. It is therefore in our greatest benefit to get every response out as quickly as possible, increasing the amount of requests we can handle per second.
Going beyond this 150 number could cause Linux to start using swap. This is bad, because it …
[Read more]
Last week I finally decided to try out micro-blogging using
Twitter. I am
not going to post much personal stuff there, but mostly technical
(especially Debian and MySQL related) stuff, here are my
updates.
Update: As suggested in the comments, I finally switched to
Identi.ca, and also deleted my account on Twitter.
The hackmysql.com website is undergoing changes. Stuff may disappear and/or be relocated at random.
Hi there,
This is my first post on the Mysql Insights Blog :) !
The idea of this blog is to share things I learn about Mysql that
might be interesting to others. Currently, I am working at a
small company where we are developing a Mysql storage engine so I
have been learning lots of cool things about Mysql.
Ivan
Recent scalability fixes in InnoDB and also Google's and your SMP fixes almost made InnoDB results acceptable in primary key lookups queries, but secondary indexes were forgotten for some time. Now having Dell PowerEdge R900 on board (16CPU cores, 16GB RAM) I have some time for experiments, and I played with queries
PLAIN TEXT CODE:
against table
PLAIN TEXT CODE: