[syslog-ng]too much time() ?

We did some maintaince on our sol9 central syslog-ng server recently running syslog-ng v1.6.4, and noticed something... truss -p on the syslog-ng process shows an abundant number of time() calls. The ratio of time() to read()/write()s were a factor of 20-40x. * This is even with use_time_recv(no); in the global options. I'm trying to understand if this is something that could be cut down some or if its a standard solaris process overhead... ?