xcode_process_num_threads default

[SageDonkey]

Hi- Sorry if this has been asked/answered before (searched and did not find) - what is the default setting for xcode_process_num_threads in 6.5.6? There is no entry in my sage.properties so I assume it defaults to something - 1, 0, or something else?

And for extra credit , will this help me with my MVP and watching HD-PVR recordings? Currently, when I try to watch, it stutters every 1-2 seconds - but my HTPC (AMD 3800+) is only at 60% (and this is while playing the same thing back on the main HTPC - looks like 10-20% is the HD-PVR playback on the main HTPC, and the other 40-50% is the transcode to the MVP - seems like if I could take advantage of my other core, I might be able to watch on the MVP) - I've seen the other HD-PVR and MVP threads and most seem to think that a quad core is needed...but I don't believe that until my dual core is 100% with MVP stuttering

Thanks!

[phelme]

xcode_process_num_threads was placed in my prop file by the installation or maybe the first time I ran the service, not sure which. it defaults to 0 (which is # cores + 1 I believe), but I don't know what the best setting is. Even though I have 4 cores, my converting seems to take longer than it did with 6.4.8. The nice thing is it now converts HD-PVR files, so I'll take it.

Originally Posted by SageDonkey

Hi- Sorry if this has been asked/answered before (searched and did not find) - what is the default setting for xcode_process_num_threads in 6.5.6? There is no entry in my sage.properties so I assume it defaults to something - 1, 0, or something else?

And for extra credit , will this help me with my MVP and watching HD-PVR recordings? Currently, when I try to watch, it stutters every 1-2 seconds - but my HTPC (AMD 3800+) is only at 60% (and this is while playing the same thing back on the main HTPC - looks like 10-20% is the HD-PVR playback on the main HTPC, and the other 40-50% is the transcode to the MVP - seems like if I could take advantage of my other core, I might be able to watch on the MVP) - I've seen the other HD-PVR and MVP threads and most seem to think that a quad core is needed...but I don't believe that until my dual core is 100% with MVP stuttering

Thanks!

[SageDonkey]

Yeah - I expected the service to put the prop in there too - but all I have is:
xcode_process_priority=idle
xcode_reduce_process_priority=true

[SageDonkey]

Just to update progress - tried to set the xcode_process_num_threads to 0, 1, 2, 3, 4, 5, 6 with no effect on the cpu (the transcoder would only goto 50% CPU - it seemed to use both cores as 1 core was not pegged, but it would not go above 50% CPU for a sustained period of time).

Going to take a look at my audio - seems that this placeshifting thread might be relevant....http://forums.sagetv.com/forums/show...358#post328358

UPDATE: Following that thread did not help. I am close to ditching the MVP and reviving some old hardware to do the trick (have an old Nvidia 6100 card and an old board with Celeron 3 Ghz somewhere - it just *might* be enough to do the trick)

[blade]

Originally Posted by SageDonkey

Just to update progress - tried to set the xcode_process_num_threads to 0, 1, 2, 3, 4, 5, 6 with no effect on the cpu (the transcoder would only goto 50% CPU - it seemed to use both cores as 1 core was not pegged, but it would not go above 50% CPU for a sustained period of time).

Same here. Sage support had said that it wouldn't max out multiple cores, but should provide better performance than before. I was really hoping it would use more than 50% though.

[phelme]

it's a mystery to me. it's suppose to change the number of working threads I believe, but I'm not sure it does. of course, for conversions I'm not sure there would be more than one active thread.

currently I have it set to 0. on a conversion that's running right now, I have 11 threads, but 10 of them are doing absolutely nothing. this has been churning for 21 hours. (an HD-PVR -> AppleTV conversion on an 8 GB file). 3 of 4 cores are being used for the process to a total of of 25% utilization.

[joe123]

Originally Posted by blade

Same here. Sage support had said that it wouldn't max out multiple cores, but should provide better performance than before. I was really hoping it would use more than 50% though.

I just upgraded from 6.4 to 6.5.59 and Transcoder.exe is running a lot faster. I have dual core Intel CPUs.

In version 6.4 trancoder.exe used to run no more than 50% (1 CPU), but now with SageTV version 6.5, transcoder.exe runs at 65% which means it is using both CPUs simultaniously.

Mine xcode_process_num_threads is set at 0, but task manager says Transcoder.exe is running with 7 threads. Does anyone know how 7 threads maps out to CPU % utilization?