Dual or Quad Core
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:3e82d1540af36c0921ea0042f9345172' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Hi,</p>\n<p>If a machine is used as Mythdora backend, frontend, web server and VMware Workstation (in order to run Windows XP) will i see the benefits of a Qaud Core or am i just wasting my money?</p>\n<p>Yoggi</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:3e82d1540af36c0921ea0042f9345172' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:fcbf57d5475902d1f5a6895bc2412677' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>It all depends on VMWare and WinXP, which should be fine unless you are using some really demanding apps in WinXp. But since VMWare emulates the hardware for the VMs... will it allow you to see all your devices? I have not played with the newer Workstation myself so I cannot say for sure. If you are running 2 images, you can dedicate 2 CPUs to each image, although MythDora will only need one.</p>\n<p>timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:fcbf57d5475902d1f5a6895bc2412677' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:8515f4154e721317d569c0a03abfd7e4' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:8515f4154e721317d569c0a03abfd7e4' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:264de7ce584a456453d2cb47a8b3b0fe' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Really it depends on how many tuners & how much load you expect to generate. I have a dual core fileserver that runs no less than 3 VMs plus serves files for me. Then my master-slave backend is a quad core that also runs no less than 3 vms at a given time (including the master backend vm). While the machine is rarely out of resources, it is quite busy when I have say 2 or 3 commflagging jobs in motion plus the VM activity. </p>\n<p>If the price difference isn\'t too great it never hurts to go big. :)</p>\n<p>Ryan</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:264de7ce584a456453d2cb47a8b3b0fe' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:a77810367563a5417b8507c62d2efe9d' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Commflagging hits the CPU that hard? I\'ve never noticed that. My system tends to get bogged down in I/O when a lot is going on. Multiple drives with the filesystem striped across them or a nice array help but I am down to one functioning SATA drive for the timemachine right now. My NLE system has two. I cannot buy anything until I get a job.</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:a77810367563a5417b8507c62d2efe9d' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:8515f4154e721317d569c0a03abfd7e4' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:8515f4154e721317d569c0a03abfd7e4' in /var/www/mythdora/html/includes/cache.inc on line 109.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:586fafc761a63609a33775be0b625501' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Yeah commflagging is pretty cpu & i/o intensive. 1 job may not be too bad but if you\'ve got multiple captures and commflagging at once it can easily overwhelm a system. I have a buddies mythbox setup to only commflag over night because his system can\'t keep up with with capturing and commflagging at the same time.</p>\n', created = 1368989938, expire = 1369076338, headers = '', serialized = 0 WHERE cid = '1:586fafc761a63609a33775be0b625501' in /var/www/mythdora/html/includes/cache.inc on line 109.
Submitted by Yoggi on January 31, 2009 - 4:48am
Hi,
If a machine is used as Mythdora backend, frontend, web server and VMware Workstation (in order to run Windows XP) will i see the benefits of a Qaud Core or am i just wasting my money?
Yoggi

MythDora uses very little CPU
It all depends on VMWare and WinXP, which should be fine unless you are using some really demanding apps in WinXp. But since VMWare emulates the hardware for the VMs... will it allow you to see all your devices? I have not played with the newer Workstation myself so I cannot say for sure. If you are running 2 images, you can dedicate 2 CPUs to each image, although MythDora will only need one.
timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle
timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle
Really it depends on how
Really it depends on how many tuners & how much load you expect to generate. I have a dual core fileserver that runs no less than 3 VMs plus serves files for me. Then my master-slave backend is a quad core that also runs no less than 3 vms at a given time (including the master backend vm). While the machine is rarely out of resources, it is quite busy when I have say 2 or 3 commflagging jobs in motion plus the VM activity.
If the price difference isn't too great it never hurts to go big. :)
Ryan
I/O is more important
Commflagging hits the CPU that hard? I've never noticed that. My system tends to get bogged down in I/O when a lot is going on. Multiple drives with the filesystem striped across them or a nice array help but I am down to one functioning SATA drive for the timemachine right now. My NLE system has two. I cannot buy anything until I get a job.
timemachine: Intel dual-core, PVR-350 in an XPC Glamor shuttle
Yeah commflagging is pretty
Yeah commflagging is pretty cpu & i/o intensive. 1 job may not be too bad but if you've got multiple captures and commflagging at once it can easily overwhelm a system. I have a buddies mythbox setup to only commflag over night because his system can't keep up with with capturing and commflagging at the same time.