Today, while browsing around, I came across a post by Jeff, a
CNET employee
who was wondering about what provides the optimal usage (assuming
a server has 16GB of RAM)? To paraphrase his question,
would it be better to use a Large RAM disk or have the MySQL live
on the hard disks?
So far I haven't used RAM disk for MySQL simply because most of
the servers didn't have 16GB of RAM and some of the databases I
worked with were quite larger than 16GB.
I assume that using RAM disk would provide a volatile
infrastructure but would certainly improve the performance. Gurus
are your thoughts? What can be the possible disadvantages of
setting up a RAM disk for large databases?
Your thoughts and comments are needed.
…
OK, we updated XServes to 10.3.9 from 10.3.7 using the following
procedure and had no problems.
First updated MySQL Server XServe to 10.3.9 and MySQL 4.0.26-
Standard for Darwin 7.9 - no issues there.
Next Web App XServes were updated from 10.3.7 to 10.3.9 using the
following procedure and no issues.
OK, we updated XServes to 10.3.9 from 10.3.7 using the following
procedure and had no problems.
First updated MySQL Server XServe to 10.3.9 and MySQL 4.0.26-
Standard for Darwin 7.9 - no issues there.
Next Web App XServes were updated from 10.3.7 to 10.3.9 using the
following procedure and no issues.
In addition to some other talks in the Java track at the MySQL Users' Conference in April, I‘ll be giving a half day tutorial on scalability and performance optimization for Java applications deployed against MySQL:
Planning, Deploying, and Diagnosing Problems of J2EE Applications
on MySQL
Mark D. Matthews, MySQL AB
Track: Java
Date: Monday, April 24
Time: 8:30am – 12:00pm
Location: Ballroom G
This tutorial covers the planning, deployment, and troubleshooting aspects of a J2EE application deployed on MySQL. Matthews will cover typical deployment scenarios and help you avoid the common mistakes made when deploying J2EE applications with MySQL, including hands-on walkthroughs of deployment and configuration of MySQL with Apache Tomcat, JBoss, …
[Read more]In addition to some other talks in the Java track at the MySQL Users' Conference in April, I'll be giving a half day tutorial on scalability and performance optimization for Java applications deployed against MySQL:
Planning, Deploying, and Diagnosing Problems of J2EE Applications on MySQL Mark D. Matthews, MySQL AB Track: Java Date: Monday, April 24 Time: 8:30am - 12:00pm Location: Ballroom G
This tutorial covers the planning, deployment, and troubleshooting aspects of a J2EE application deployed on MySQL. Matthews will cover typical deployment scenarios and help you avoid the common mistakes made when deploying J2EE applications with MySQL, including hands-on walkthroughs of deployment and configuration of MySQL with Apache Tomcat, JBoss, Hibernate and Spring.
In addition, …
[Read more]In addition to some other talks in the Java track at the MySQL Users' Conference in April, I‘ll be giving a half day tutorial on scalability and performance optimization for Java applications deployed against MySQL:
Planning, Deploying, and Diagnosing Problems of J2EE Applications
on MySQL
Mark D. Matthews, MySQL AB
Track: Java
Date: Monday, April 24
Time: 8:30am – 12:00pm
Location: Ballroom G
This tutorial covers the planning, deployment, and troubleshooting aspects of a J2EE application deployed on MySQL. Matthews will cover typical deployment scenarios and help you avoid the common mistakes made when deploying J2EE applications with MySQL, including hands-on walkthroughs of deployment and configuration of MySQL with Apache Tomcat, JBoss, …
[Read more]Oracle bought 2 companies which develop 2 open source storage engines that MySQL uses. Those storage engines are both transactional.
There’s the possibility Oracle does the stupid (from a PR perspective) move of making those databases proprietary. But it’s OPEN SOURCE right now. Which means that it’ll branch.
Worst case scenario? The developing stops here, and InnoDB and BDB never get any more functional than they currently are.
The “bad” scenario? MySQL is a company. With hired staff. They pay the hired staff to get familiar with the source code for those engines and continue to develop them. Hence the branch.
The likely scenario? 1) Oracle tries to have a pluggable storage engine architecture like MySQL. Oracle Express or Lite or whatever would be free with those engines, pay with the original. 2) Oracle tries to go on the good partnership of “we support MySQL by developing their architecture, we’re …
[Read more]I just stumbled across a recently discovered security issue in MySQL while I made use of the general query log today (which is usually deactivated on our servers) to track down the behaviour of some legacy applications: If you grant access to possibly untrusted users, you shouldn't count on the general query log to supervise their activities.
The original security advisory was published one week ago by 1dt.w0lf and also reported as bug #17667.
A user can hide any queries from the general query log by just embedding a
NUL character (ASCII 0). The general query log will
treat that as an end of string and skip all following characters.
To hide your queries just add a comment including the …
Often, a new version of OS can dictate changes to WO version, XCode version and/or java version. My primary objective is to make sure I have stable WO development that is compatible with the deployment server OS version. Sometimes upgrading my development Mac can cause me to have to use a new version of the OS. In any case, this blog entry is a non-comprehensive table of compatible versions of the various environment elements. I also include MySQL version that works well with that combination since that's what I use.
Often, a new version of OS can dictate changes to WO version, XCode version and/or java version. My primary objective is to make sure I have stable WO development that is compatible with the deployment server OS version. Sometimes upgrading my development Mac can cause me to have to use a new version of the OS. In any case, this blog entry is a non-comprehensive table of compatible versions of the various environment elements. I also include MySQL version that works well with that combination since that's what I use.