| T O P I C R E V I E W |
| Webbo |
Posted - 28 April 2010 : 23:57:00
Hi All,
I've got an issue with our host that basically I was wondering if anyone could offer advice on..
The problem is my site is on a dedicated windows server, the basic specs are as follows:
Dell server
Windows Server 2008
Quad Core X3330 (2.66GHz) Intel processor
4GB Ram
2 x 450GB SAS hard drives
Tier 1 network
...and on that server I have another website with an online store
The main site has approx 18million hits per month with up to 300 users on at anyone time and uses approx 160GB data transfer per month
The second site has a fraction of that, in the region of 4,000 hits per month
Both sites use MySql,
The first site uses mainly asp and the Snitz forum is gnerally where most of the traffic goes to
The second site uses Zencart shopping cart software
The problem is that every now and again MySql bombs out, it grinds to a halt and generally results in a server reboot to resolve the problem.
There is nothing specific that causes this but it does seem to happen at the busiest times, but then again as previously posted it does not happen all of the time.
We've used extended server logs to see if there is a code issue or something else that is causing the problem and nothing has come up out of the ordinary, not even at times when the problem arises.
The only thing we could come up with was the number of databse connections that might be causing the problem and this was upped to 800 simultainious connections, but still the problem persists.
I could up it further but there seems little point as the maximum number of connections we've had has been approx 650
Now, the hosts have suggested that we might need to look at putting a second server linked to the first using a router and balancing the load between the two servers as their engineers reckon the problem is the demand on the existing server - this is a new server by the way
The other option suggested was to move the second site onto a second server. The first option was the prefered one of the engineers.
Now, my problem is I do not know enough about server specs and abilities to know if what I'm being told is correct, or whether or not the existing server is more than capable of handling the two websites by it self and that the problem is server related
Apparantly the enginners maintain that the server is running as it should and that there are no issues with it other than the apparent crashes linked with MySql
We are using MySQL 5.1.44 and IIS 6.0
The size of the first website databsase is approx 1.6GB
The second is a mere 1,032 kB
Tbh, and the reason why I'm asking on here, is I do not have a great deal of confidence in our host. We ended up with them after the original host of 9 years sold the hosting side of the business to them, including us and our original server.
The original server was damaged during relocating to a new server centre and as a result we were given this new server which is of a higher spec than the original.
The original server never really had any issues, definately nothing like this, and so I'm inclined to think that the problem is with the new server although I'm being told adamantly that it isn't.
Is there anyone on here that could let me know based on the above if the server is capable of handling the traffic and/or whether or not you think it could be an issue with the hosting, or even that the information I'm being given is correct?
Many thanks,
Dave
|
| 9 L A T E S T R E P L I E S (Newest First) |
| pierretopping |
Posted - 27 May 2010 : 05:30:31
glad its all sorted  |
| Webbo |
Posted - 24 May 2010 : 15:58:47
Just an update...
Since questioning my hosts further, and using a few points made on here, everything seems to have miraculously sorted itself. It sure smacks of coincidence lol but I'm not going to grumble as we're now getting the performance and reliability that was expected
Once again, many thanks
Dave |
| pierretopping |
Posted - 30 April 2010 : 04:14:33
quote:
Originally posted by Webbo
How much work would be required to migrate a 1.6gb database over onto SQL server?
Hi,
We moved to SQL server some 16 months ago, A lot better. You can use the personal version of SQL as well (but check the size limitation of the database if your going to use that version). A good guide is available on this site for the migration.
I would set a virtual system and use that to get your procedures ready for when you switch to the new db engine on your live system. Also, get some trusted users on the new DB so they can do some tests in-case you run into some issues with the ASP code.
Good luck 
Pierre |
| ruirib |
Posted - 29 April 2010 : 17:59:26
The amount of work is not dependent on the size. You will need to create the table structure, which may give a bit of work but can be done with some degree of ease. Then you just need to use SSIS to migrate the data, but that is pretty straightforward.
The database will be bigger in size and it may need some tuning. Indexing strategies can be a bit different. |
| Webbo |
Posted - 29 April 2010 : 17:53:23
Thanks everyone, it has given me some questions I can ask the hosts
It is definately a dedicated not virtual server Classicmotorcycling
How much work would be required to migrate a 1.6gb database over onto SQL server? |
| pierretopping |
Posted - 29 April 2010 : 07:55:35
Check out the following, might help with the My-sql side of thins.
http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html
|
| Classicmotorcycling |
Posted - 29 April 2010 : 06:57:11
The server can handle the load of the traffic, not sure on the MySQL as I have seen it crash on many occassions with smaller databases. Been dealing with IIS most of my IT career, which included working in designing of some of the Internet banking functions of one of the large banks here in Australia which was getting over 1 million hits a day running on Windows 2000 and 1Gb RAM.
The other thing is that the server specs sound like that they are Virtual Server settings, how I know you ask, well I work for a large Internet Service Provider now and they sound like the speed of CPU's that VMWare normally puts out. If it is a Virtual Server, then you are sharing resources with others to compete for the CPU, RAM and in some cases Hard Drive space even though it says you have the 2 x 450GB as the server may not be using the resources all the time. Some companies over share Virtuals and blame other things.
First thing to do is look at the IIS log files, then look at the Event Viewer when it dies, that should give you and idea of what maybe happening around the time the MySQL bombs out and should also let you know if it is a coding issue. You could also check your code on the server to make sure that it is not holding the DB open for longer than required. |
| ruirib |
Posted - 29 April 2010 : 05:44:43
I don't really trust MySQL that much. I have experienced similar situations and recently even an upgrade to the MySQL version in use was needed. My impression is that the reliability of MySQL leaves much to be desired, specially when compared with SQL Server, for example.
I know this doesn't help much, but it's my own experience.
Anyway, what do they are basing on to say the issue is server load? Do they have data like average CPU use, etc, to justify the need for a second server? |
| pierretopping |
Posted - 29 April 2010 : 04:19:53
Hi,
Have you checked in the systems logs of 2008 ?
With only 4GB of memory, that could be issue. How much memory is being used before you do the re-boot ?
My-sql can sometime hog memory, or you could have a memory leak.
Pierre |
|
|
