MySQL 3.23.58 -> MySQL 4.1.8 ? [Archive] - vBulletin Community Forum

View Full Version : MySQL 3.23.58 -> MySQL 4.1.8 ?

TechGuy

Thu 6th Jan '05, 2:28am

Howdy all,

I'm currently running a rather old version of MySQL (3.23.58) and I'm considering upgraing to 4.1.8.

Is 4.1.8 recommended and accepted for vBulletin installations?

Are there any major considerations with such an upgrade, in particular with vBulletin? Whlie I have recent backups, I obviously want to minimize downtime and potential problems / corruption.

Thanks!

Zachery

Thu 6th Jan '05, 2:52am

You would be best off with MySQL 4.0.20/22 at this time.

TechGuy

Thu 6th Jan '05, 12:33pm

Thanks for the reply! Why is that? Also, I heard that there are some difficulties in moving from 4.0.x to 4.1.x (that I thought I might avoid by jumping to 4.1). Thanks again!

AKosygin

Mon 10th Jan '05, 1:22am

In most default MySQL 4.1 installations, you just need to make sure of two things which I have detailed here:

http://www.vbulletin.com/forum/showthread.php?t=125929

TechGuy

Mon 10th Jan '05, 1:25am

Thanks for the reply! I upgraded to 4.0.23 already and had no problems, so I guess I'll stick with that for now.

Thanks again, though!

BamaStangGuy

Mon 10th Jan '05, 1:33am

Thanks for the reply! I upgraded to 4.0.23 already and had no problems, so I guess I'll stick with that for now.

Thanks again, though!
Did you notice a huge performance increase?

Do you have query cache enabled?

I know I noticed a huge increase

Might want to post in the server config thread for the best my.cnf configuration to use

TechGuy

Mon 10th Jan '05, 1:37am

I used the my-huge.cnf that was included with the package. I had to increase the maximum packet (1MB was way too small)... Query Cache is enabled at 32MB. I haven't noticed any great performance increase, but to be honest our database server wasn't under that heavy of a load anyway (it's mostly the web servers that get the loads).

Uptime: 49248 Threads: 5 Questions: 2399796 Slow queries: 81 Opens: 508 Flush tables: 1 Open tables: 502 Queries per second avg: 48.729

BamaStangGuy

Mon 10th Jan '05, 2:42am

I used the my-huge.cnf that was included with the package. I had to increase the maximum packet (1MB was way too small)... Query Cache is enabled at 32MB. I haven't noticed any great performance increase, but to be honest our database server wasn't under that heavy of a load anyway (it's mostly the web servers that get the loads).
I would still recommend posting in the server config forum. It can only help make things faster for your users and save bandwidth