Mysqld.exe needs 20% CPU (2 Viewers)

[hanfmaster]

MediaPortal Version: 1.2.1
MediaPortal Skin: StreamdMP
Windows Version: Server: Win7 /Client:Win7
CPU Type: AMD Phenom X2 550@X4 B90/Intel T7500
HDD: Samsung HD501J/WDC WD2500
Memory: 4GB DDR3/2GB DDR3
Motherboard: MSI 880GMA-E45/Dell
Video Card: 880g/9600m GT
Video Card Driver:
Sound Card: realteck HD/SigmaTel HD
Sound Card AC3:
Sound Card Driver: / 6.10.0.56.14
1. TV Card: terratec cinergy s2 / is client
1. TV Card Type: DVB-S2
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider: Astra 19.2°E
HTPC Case:
Cooling:
Power Supply: 300W
Remote:
TV: Samsung 2232BW
TV - HTPC Connection: dvi

Is it normal that the mysqld.exe needs, for just a short time period , 20% CPU?
Most of the time it is <1% CPU usage.
Actually this would not bug me, but my PWM-Fan gets scared and starts to rotate faster.

 

[Holzi]

AW: Mysqld.exe needs 20% CPU

Maybe this has something to do with the EPG grabbing?! I don't know..

 

[Lehmden]

AW: Mysqld.exe needs 20% CPU

Hi.
This is normal, I fear. Every now and then the CPU Load raises. I think this is due some database work (index, table check,...). If you disable EPG completely this will happen also, so EPG could not be the reason. To be precisely, this happens also, if you did not have MP installed at all.

 

[hanfmaster]

AW: Mysqld.exe needs 20% CPU

Would it help if i use SQL Server 2008?

 

[Lehmden]

AW: Mysqld.exe needs 20% CPU

Hi.
MS SQL also did some Database Work in Background. So there should be not that big difference.

 

[Paranoid Delusion]

This db using 20%, mine does this about 8am every morning for about 5 minutes, does it cause any other problem would be my worry, as no effects seen after a couple of years, I'm really not bothered by it any more and just ignore it.

 

[hanfmaster]

I reinstalled win7 today and did install MS SQL, bit tricky but with the wiki it worked.
So we'll see...