RR wrote:
Hi Leo,
Sorry mate, I thought I had done some research but I only found one
reference to it somewhere and it stated that if you have more than one
VM running inside VMWare server v1.0, then there are timing issues
where the clock seems to vary randomly. I figured that didn't apply to
Thanks Leo, great explanation. Will do some additional research and
try out a few tests if I can find the time to setup a small load-test
sort of a scenario but it does sound from your explanation that
symmetric multi-processing is what we need to share the load and get
double or close to double
RR wrote:
Also, at every start of (*), the show translation command shows
different transcoding times without changing a single thing in the
system in the way of config etc. Why is that?
Because I believe they are calculated based on current system load.
Whenever you'd like to see them
Ranj,
Sigh :(. It would have save you and us a lot of time if you'd mentioned
this fact earlier:
Oh also, note that this system is running inside of a Virtual Machine
with 768 RAM and a 3.4GHz CPU although NO other VM is active on this
VM server.
When running in a VM (like VMWare), the timing
HI Mojo,
thanks for that. Sounds like a hidden option. It doesn't show up when
I do a tab after I type show translation on the CLI.
But to respond to your comment, I thought that's what it was, as in
calculated based on the current load of the system but the fact is
that there is absolutely
Hi Leo,
Sorry mate, I thought I had done some research but I only found one
reference to it somewhere and it stated that if you have more than one
VM running inside VMWare server v1.0, then there are timing issues
where the clock seems to vary randomly. I figured that didn't apply to
me since I
Hi all, (2nd attempt)
this is probably a weird question and something I'm not doing right
but I got this bizarre thing going on here. When I boot the system
with the SMP kernel and compile (*) with the smp kernel source
(actually even if I don't compile, but as long as I boot into the SMP
Check the timer frequency, it might have a different setting on the two
kernels.
RR wrote:
Hi all, (2nd attempt)
this is probably a weird question and something I'm not doing right
but I got this bizarre thing going on here. When I boot the system
with the SMP kernel and compile (*) with
Hi Zoa,
thanks for responding. Ok, now where do I find this? I'm running
2.6.9-34.0.1 kernel. I tried doing a bit of search and it seems like
that the ability to change the frequency doesn't appear till 2.6.13.
Am I looking at the right thing? Any hints?
RR wrote:
Hi Zoa,
thanks for responding. Ok, now where do I find this? I'm running
2.6.9-34.0.1 kernel. I tried doing a bit of search and it seems like
that the ability to change the frequency doesn't appear till 2.6.13.
Am I looking at the right thing? Any hints?
You need to provide more
Hi there,
sorry I wasn't sure exactly where to start so didn't know what info to
provide. Now that I know, here's the info
1) using a P4 w/HT
2) Using CentOS 4.3 with the 2.6.9-34.0.1-smp (Note, this was
installed through an rpm, but the (*) and zaptel code is being
compiled against the source
11 matches
Mail list logo
