Hi again,
I don't think, that there are longer or shorter processes. Since I installed
the 2nd CPU (933MHz for Compaq ProLaint380), I have these logenties.
For example, I have a site, which supports more languages (at this time
english and german only). On one site, I installed a JavaScript-Calender and
the name of the months will be selected from the database in the correct
language the customer wanted it. The mysql-logs look like this, when I
called the calender and the name of month should be in german:
030317 16:09:54 22669 Init DB calenderDB
22669 Query SELECT de FROM general_lang WHERE def =
'jan'
030317 16:09:58 22669 Query SELECT de FROM general_lang WHERE def =
'feb'
030317 16:09:54 22669 Query SELECT de FROM general_lang WHERE def =
'mar'
030317 16:09:58 22669 Query SELECT de FROM general_lang WHERE def =
'apr'
22669 Query SELECT de FROM general_lang WHERE def =
'mai'
030317 16:09:54 22669 Query SELECT de FROM general_lang WHERE def =
'jun'
030317 16:09:58 22669 Query SELECT de FROM general_lang WHERE def =
'jul'
030317 16:09:54 22669 Query SELECT de FROM general_lang WHERE def =
'aug'
030317 16:09:58 22669 Query SELECT de FROM general_lang WHERE def =
'sep'
030317 16:09:54 22669 Query SELECT de FROM general_lang WHERE def =
'okt'
22669 Query SELECT de FROM general_lang WHERE def =
'nov'
030317 16:09:58 22669 Query SELECT de FROM general_lang WHERE def =
'dez'
I don't think, that selecting the german word for february, april and july
needs more cpu than march, june or october.
There is also another thing; I in one database some ISO short forms, which
stands for some languages. For example: de -> german, en -> english, it ->
italian and so on. So, if one customer wants to see details of one person
which works for our office, he maybe doesn't know the meaning of de, en, it.
So this shortforms will also translated to his prefered language. The
mysql-logs looks like this:
030317 15:20:58 22560 Query SELECT def FROM lang_sprachkuerzel WHERE
isoKuerzel = 'en'
030317 15:20:57 22560 Query SELECT en FROM general_lang WHERE def =
'englisch'
22560 Query SELECT def FROM lang_sprachkuerzel WHERE
isoKuerzel = 'hr'
030317 15:21:00 22560 Query SELECT en FROM general_lang WHERE def =
'kroatisch'
030317 15:20:57 22560 Query SELECT def FROM lang_sprachkuerzel WHERE
isoKuerzel = 'fr'
030317 15:21:00 22560 Query SELECT en FROM general_lang WHERE def =
'franzoesisch'
030317 15:20:57 22560 Query SELECT def FROM lang_sprachkuerzel WHERE
isoKuerzel = 'it'
030317 15:21:00 22560 Query SELECT en FROM general_lang WHERE def =
'italienisch'
030317 15:20:57 22560 Query SELECT def FROM lang_sprachkuerzel WHERE
isoKuerzel = 'ru'
030317 15:21:00 22560 Query SELECT en FROM general_lang WHERE def =
'russisch'
A PHP script split the language-string which was for this example:
en,hr,fr,it,ru. Then the script initialize a mysql query (look for the
definition of _en_). mysql sends back: _englisch_. Then the script
initialize a translation query (look for the english word for _englisch_).
mysql send back _english_. Only after this steps, the php-script starts
again with _hr_ and so on. So when mysql made the logentry _SELECT en FROM
general_lang WHERE def = 'englisch'_, mysql got the the query result from
_SELECT def FROM lang_sprachkuerzel WHERE isoKuerzel = 'en'_. But this query
result was in the past and not in the future.
That's the funny thing I'm thinking of. Before I upgraded my server with the
2nd cpu, the logs where _normal_.
Rgds, Peter
> -----Original Message-----
> From: Gelu Gogancea [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 17, 2003 4:48 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: mySQL activity logging on a dual prozessor maschine
>
>
> Hi Peter,
> ----- Original Message -----
> From: "Peter Stoehr" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: "Gelu Gogancea" <[EMAIL PROTECTED]>
> Sent: Monday, March 17, 2003 3:56 PM
> Subject: RE: mySQL activity logging on a dual prozessor maschine
>
>
> > Hi Gelu,
> >
> > thanks for your message. But I'm not confused about the timeformat, I'm
> > confused of the order the logs are.
> >
> > 1st: 19:31:18
> > 2nd: 19:31:20
> > 3rd: 19:31:18 (!)
> > 4th: 19:31:20 (!)
> Indeed...this is a little strange.If we suppose that your computer clock
> work fine,remain only idea about time processing.It's possible to be some
> "shorter" processes which can running on the same period of time with the
> "longer" processes.That means can be a process(shorter time running/easy
> process) which is started after another process is already started(longer
> time running/heavy) but is finished before the process which was already
> started.In this situation can make sense because this processes
> write on the
> log file (the starting time) after *they* are succesfully finished.
>
>
> Regards,
>
> Gelu
> _____________________________________________________
> G.NET SOFTWARE COMPANY
>
> Permanent e-mail address : [EMAIL PROTECTED]
> [EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
