This has nothing about how accurate the time is... Its more how long time
it takes to get information from gettimeofday().
Let say they uses gettimeofday every tick, it will add up to a lot of
calls. If the server do 100 calls per second and it takes 10+ms to get
answer from gettimeofday it will
I just made the test again today with a fresh updated 6.1 server.
I now get much better results... the highest number is down to 2.5ms.
average highest number is now 0.8ms. This is when hlds is running.
Never the less it still does not perform as well as 4.x in the low and
average account. And
--
On Sun, 4 Jun 2006 12:13:47 -0700
Alfred Reynolds [EMAIL PROTECTED] bubbled:
Both server engines use the gettimeofday() call to work out elpased
time. If that time moves significantly during a frame then the next
frame will not run properly (you would see a one frame glitch on the
server).
gettimeofday() replaced times(), at least on freebsd. also,
gettimeofday()'s results will change, depending on if your OS uses
ACPI, TSC, HPET, 8254 etc..
I don't think RDTSC will work on SMP machines.
Personally, I think gettimeofday() is alot better than what microsoft
has for timekeeping.
--
On Tue, 06 Jun 2006 05:31:19 -0400
Gary [EMAIL PROTECTED] bubbled:
gettimeofday() replaced times(), at least on freebsd. also,
gettimeofday()'s results will change, depending on if your OS uses
ACPI, TSC, HPET, 8254 etc..
gettimeofday replaces times? The two functions are for a different
In a bold display of creativity, Martin Zwickel wrote:
Personally, I think gettimeofday() is alot better than what microsoft
has for timekeeping.
No clue what Microsoft offers for timekeeping.
Sundials, is the inevitable answer ;)
--
Eric (the Deacon remix)
On Tue, 6 Jun 2006, Martin Zwickel wrote:
--
On Tue, 06 Jun 2006 05:31:19 -0400
Gary [EMAIL PROTECTED] bubbled:
gettimeofday() replaced times(), at least on freebsd. also,
gettimeofday()'s results will change, depending on if your OS uses
ACPI, TSC, HPET, 8254 etc..
gettimeofday
kama wrote:
Maybe finally I have found something that can explain why I get
strange
chokes on my servers every now and then?
Its a known fact gettimeofday is significantly heavier
on freebsd than it is on linux which uses a cheap version.
There are various proposed fixes none of which have
None of this matters squat, as hlds/srcds are developed for Microsoft's
x86 Win32 platform and Linux's x86 platform. gettimeofday shouldn't be
THAT much of a problem for hlds/srcds unless you are not running ntpd.
You should be running it on Win32, Linux, or any other production
system. If
hence the question to alfred...
/Bjorn
On Sun, 4 Jun 2006, Gary wrote:
Some OS's have very expensive gettimeofday calls..
At 04:04 PM 6/4/2006, kama wrote:
Could this cause choke if the gettimeofday() is really choppy and time
consuming?
/Bjorn
On Sun, 4 Jun 2006, Alfred Reynolds
Not as much a bad hardware clock as a OS related issue.
Lets say gettimeofday() uses X ts (time slices) in OS A that counts as a
extremely accurate call. If OS B uses 2X-7X ts in a random fashion, could
this cause any choke problems?
/Bjorn
On Sun, 4 Jun 2006, Alfred Reynolds wrote:
In
Under linux 2.4 and earlier the gettimeofday() call has around a 10msec
increments between updates (i.e it has nanosecond resolution but the OS
only changes the time once per scheduler update). The larger the wall
clock time between updates to the clock value the worse the server will
perform, and
Erik Hollensbe wrote:
Are the daemons time-sensitive with regard to the system time? The
reason is, we had a few servers that were out of sync, and I resynced
them manually, then the inevitable flood of support requests came in.
I can confirm this problem exists. It's not just a simple frame
Erik Hollensbe wrote:
Are the daemons time-sensitive with regard to the system time? The
reason is, we had a few servers that were out of sync, and I resynced
them manually, then the inevitable flood of support requests came in.
I guess my second question could be: is there a reason this
On Jun 4, 2006, at 9:42 AM, m0gely wrote:
Erik Hollensbe wrote:
Are the daemons time-sensitive with regard to the system time? The
reason is, we had a few servers that were out of sync, and I resynced
them manually, then the inevitable flood of support requests came in.
I guess my second
If you are talking about cumulative clock drifting, yes. As far as
it's interaction to hlds etc, I don't know :)
I know the quartz is sensitive to temperatures and if it gets too
warm/BIOS issue, it will drift more.
At 03:02 AM 6/4/2006, Erik Hollensbe wrote:
Are the daemons time-sensitive with
On Jun 4, 2006, at 11:37 AM, Gary wrote:
If you are talking about cumulative clock drifting, yes. As far as
it's interaction to hlds etc, I don't know :)
I know the quartz is sensitive to temperatures and if it gets too
warm/BIOS issue, it will drift more.
Sorry, I meant the daemons. The
Could this cause choke if the gettimeofday() is really choppy and time
consuming?
/Bjorn
On Sun, 4 Jun 2006, Alfred Reynolds wrote:
Both server engines use the gettimeofday() call to work out elpased
time. If that time moves significantly during a frame then the next
frame will not run
I don't see how it could cause a crash, but with the complexity of the
simulation engine in Source I guess this is possible. Get a better clock in
your server.
- Alfred
Ondrej Hošek wrote:
So much for Monday... ;)
How can a server actually crash when the time is reset? Is there any
part of
In theory as the network system uses the gettimeofday() value to work
out network usage, but you would need a really really bad clock.
- Alfred
kama wrote:
Could this cause choke if the gettimeofday() is really choppy and time
consuming?
/Bjorn
On Sun, 4 Jun 2006, Alfred Reynolds wrote:
On Jun 4, 2006, at 2:27 PM, Alfred Reynolds wrote:
I don't see how it could cause a crash, but with the complexity of
the simulation engine in Source I guess this is possible. Get a
better clock in your server.
Yeah, these machines had been long-neglected and I was doing a time
sync on them,
Some OS's have very expensive gettimeofday calls..
At 04:04 PM 6/4/2006, kama wrote:
Could this cause choke if the gettimeofday() is really choppy and time
consuming?
/Bjorn
On Sun, 4 Jun 2006, Alfred Reynolds wrote:
Both server engines use the gettimeofday() call to work out elpased
22 matches
Mail list logo
