I was wondering if a MySQL database run faster on Windows server 2019 or on Windows 10.
Are the performance based on the operating system or just on the installed hardware?
The only significant differences are
HDD (slower) or SSD (faster)
Network latency (now close are the client and server)
Other things:
CPU -- Today's CPUs don't have much range in speed. And most queries are fast enough that a CPU speed difference is usually not noticeable
CPU cores -- See CPU.
RAID with hardware write cache -- Beneficial for heavy write situations.
OS -- Only if you have very little I/O and network latency might you even be able to measure an OS speed difference.
Related
I have two database servers.
Server A has 128GB memory with 75% for buffer_pool
Server B has 64GB memory with 25% for buffer_pool
There is no activity on Server A but an ALTER on a 220 GB table.
There is replication activity on Server B on ALTER on same 220 GB table.
Server B completes in half the time.
Can someone explain what might cause this behavior? All settings across Server A and B are similar except for memory and buffer_pool alotments.
Both are identical OS and Server A has 16 core CPU, while Server B has 8 core.
Not everything is main memory, in my case, factors like OS and CPU make a big difference. I tested same DB in different machines (for a project I worked on), and found a better general performance in a Linux i5-6200U and 8gb DDR4 machine than a W7 i7-4000 and 16gb DDR3 (around a 20% better performance)
I'm in the process of both virtualizing and updating an old Linux server running a reporting system developed in house (Apache, MySQL, PHP).
The old physical server is running 64-bit Ubuntu 10.04.3 LTS, MySQL 5.1.41 and PHP 5.3. The server has an Intel Xeon CPU X3460 # 2.80GHz (4 cores), 4GB RAM.
We have ESXI 5.5 running on an HP DL380G6 with 2 x Intel Xeon X5650 6 Core 2.66ghz and 32GB RAM.
I created a new VM with 4 cores and 4GB RAM, and did a clean install of 64-bit Ubuntu 16.04.4 LTS, MySQL 5.7.21 and PHP 7.0, migrated our app, and everything is running much slower. I believe it's MySQL because when doing the same direct query on the old physical server vs the new virtualized one, queries can take 8 seconds (VM) instead of 1 (Physical). The tables all have appropriate indexes, running "EXPLAIN" on each server provides the same results, yet one is substantially slower. When a page is running numerous complex queries, it can take a minute+ to load instead of a few seconds.
Any idea why this can be? Same dataset, same query, same engine (MyISAM). The VM has much more recent versions of everything, same number of cores and same RAM. I even tried doubling the VM CPU to 2 sockets, 4 cores and 8GB RAM, and it doesn't seem to have a substantial impact.
I've compared the MySQL configuration and nothing is jumping out at me at being very different.
What might I be missing here? Is it the virtual host hardware?
Did you upgrade the vmware tools? if not do so.
Then, on this ESXi host, do you have other VMs on it? If yes, I would advise you to create a resource pool and then configure the resource limits.
In the resource pool the amount of resource you assign will be in a way reserved for your VM, so you won't have to share with other VMs.
I have an application on my server that uses many database requests to a reasonable simple and small database (10Mb size).
The number of simultaneous requests can be around 500. I have an Apache & Mysql server running on linux with 8GB RAM and 3 cores.
I've upgraded the server recently(from 512mb to 8GB), but this is not having effect. It seems that the aditional CPU and RAM is not being used. Before the CPU hit 100%, but after the upgrade I still get status WARN at only 40% CPU usage:
Free RAM: 6736.94 MB
Free Swap: 1023.94 MB
Disk i/o: 194 io/s
In the processes, the mysqld cpu usage is 100%.
I can't figure out what the right settings are to make the hardware upgrade work for mysql and MyISAM engine.
I have little experience with setting up and configuring a server, so detailed comments or help are very welcome.
UPDATE #1
the mysql requests are both readers and writers from a large number of php scripts.
I have a SQL Server 2008 in production environment (Windows 2003 -64 bit) and
it is consuming 10 GB memory of installed 20GB. Is this normal behavior or is there anything wrong with the configuration ?
P.S. I have hosted one web application which is used by hundreds of users concurrently everyday .
SQL Server reserves memory which is why you are seeing high peaks. It might show up as using 10GB in your Task Manager, but the real memory usage can be checked from within the Management Studio.
Also, you can establish upper and lower limits to the amount of memory (buffer pool) used by the SQL Server database engine with the min server memory and max server memory configuration options.
Check this article out http://support.microsoft.com/kb/321363
Microsoft has adopted the strategy for memory management that any unused memory is wasted memory. Microsoft's newer OS's and SQL Server versions will allocate more memory for caching, until the system requests it for other purposes.
So, what you are seeing is probably normal.
Much of that allocated memory can be released to other applications as needed. As distressing as that memory usage may seem, it is not as dire a situation as it may appear.
There is nothing wrong with that behavior, SQL is just caching your data. If there is something else you'd like to use that memory for you can configure SQL Server to use less, however, configuring it that way may make queries slower.
How good it'd be to have 64 bit MySQL on 64 bit Linux ofcouse?
Presently I have 32bit Mysql / OS but 64bit hardware.
Shall I consider upgrade? What advantages do I have?
You will get the main advantage of 64bit software - you will be able to address more RAM
What advantages do I have?
Potentially bigger in-memory caches. And big caches can really help database performance ... in some cases. However, I've also noticed evidence that suggests that there is a limit to which application caches help, and that in some situations a OS level file caches work better at reducing disc IO delays.
For some hints on how 64bit MySQL (with appropriate tuning) might help, read How MySQL Uses Memory from the MySQL manual.