I was waiting for others' comments, but as they lacked, here goes.<br><br>First of, do you really have a problem with too many gettimeofday() syscalls from your<br>erlang program, or is it just a premature guess of a bottleneck in some code you
<br>will write? I suggest you go with erlang:now() and see.<br><br>If your guess would indeed be true, then you could look at the 'timer' module. There<br>are some functions there that could be interesting for 'driving' a timer you keep in a
<br>process.<br><br><div><span class="gmail_quote">On 5/22/06, <b class="gmail_sendername">Gaspar Chilingarov</b> <<a href="mailto:nm@web.am">nm@web.am</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all!<br><br>I've searched erlang documentation but without any positive results...<br><br>Are there a way to get unix_timestamp at low cost? Even not-so-precise<br>as erlang:now() - it may be even a little bit illegal - say several
<br>seconds back of real time ...<br><br>I wish to have time recorded with a several second precision, but making<br>too much erlang:now() calls is not a good idea -- at least<br>gettimeoffay() for C applications can create serios slowdown of program.
<br><br>Seems, that the only way to achieve this is a creating standalone<br>process and requesting timestamp from it?<br><br><br>--<br>Gaspar Chilingarov<br><br>System Administrator,<br>Network security consulting<br><br>
t +37491 419763 (mob)<br>i 63174784<br>e <a href="mailto:nm@web.am">nm@web.am</a><br></blockquote></div><br>