Messages in this thread | | | Subject | Re: 2.4.23aa2 (bugfixes and important VM improvements for the high end) | From | Peter Zaitsev <> | Date | Sat, 06 Mar 2004 22:50:08 -0800 |
| |
On Fri, 2004-03-05 at 07:02, Ingo Molnar wrote: > * Andrea Arcangeli <andrea@suse.de> wrote: > > > I thought time() wouldn't be called more than 1 per second anyways, > > why would anyone call time more than 1 per second? > > if mysql in fact calls time() frequently, then it should rather start a > worker thread that updates a global time variable every second.
Ingo, Andrea,
I would not say MySQL calls time that often, it is normally 2 times per query (to measure query execution time), might be couple of times more.
Looking at typical profiling results it takes much less than 1% of time, even for very simple query loads.
Rather than changing design how time is computed I think we would better to go to better accuracy - nowadays 1 second is far too raw.
-- Peter Zaitsev, Senior Support Engineer MySQL AB, www.mysql.com
Meet the MySQL Team at User Conference 2004! (April 14-16, Orlando,FL) http://www.mysql.com/uc2004/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |