From: Frank Geurts (geurts_at_rice.edu)
Date: Fri Mar 07 2003 - 16:19:13 EST
-------- Original Message --------
Subject: Re: FYI: L2 latencies
Date: Fri, 07 Mar 2003 16:03:42 -0500
From: Zoran Milosevich <zoran.milosevich_at_cmu.edu>
To: Frank Geurts <geurts_at_rice.edu>
CC: startrig-hn_at_connery.star.bnl.gov, "Tonko A. Ljubicic"
<tonko_at_bnl.gov>, Jeff Landgraf <jml_at_bnl.gov>
References: <Pine.GSO.4.33.0303071319290.23441-100000_at_daq.star.bnl.gov>
<3E68E884.DD3ED6EE_at_cmu.edu> <3E68F864.2060006_at_rice.edu>
Hi Frank -
OK, thanks for the information. Anything before run 4065050, we can perhaps
understand. After this run, L2 was updated, so there should not be a
problem.
At least from l2. Below is the Level 2 logging information we have for
that run.
NOTES - l2Accept is the time between when l2 gets a token from l1 and sends
a L2_ACCEPT to l1. l2Process is the time between when sending an L2_ACCEPT
and sending token (and data) to GB. Units are in msec. I only flag here
times of
L2Process greater than 5.0 OR l2Accept greater than 2.0. I see one 11
msec and
a couple 7 msec L2_ACCEPT times, but nothing greater than that.
I don't know if this helps you track this down.
Zoran
start
run4065052.l2
evt 2875 token 2875
+++++++++++++++++++++++ l1 1047000877.264014
l2Accept 2.158999
l2Process 0.277042
evt 3685 token 3685
l2Accept 1.325965
l2Process 10.453105
evt 8623 token 440
+++++++++++++++++++++++ l1 1047001000.314101 diff from last 123.050087
l2Accept 2.210021
l2Process 0.285983
evt 13774 token 1498
+++++++++++++++++++++++ l1 1047001105.721734 diff from last 105.407633
l2Accept 2.397895
l2Process 1.208067
evt 15282 token 3012
+++++++++++++++++++++++ l1 1047001135.718507 diff from last 29.996773
l2Accept 7.120967
l2Process 2.290964
evt 15778 token 3498
+++++++++++++++++++++++ l1 1047001145.748208 diff from last 10.029701
l2Accept 3.913999
l2Process 1.321912
evt 16283 token 4011
+++++++++++++++++++++++ l1 1047001155.761646 diff from last 10.013438
l2Accept 3.289938
l2Process 1.288056
evt 27000 token 2458
+++++++++++++++++++++++ l1 1047001370.954638 diff from last 215.192992
l2Accept 4.662991
l2Process 0.589013
evt 27248 token 2703
+++++++++++++++++++++++ l1 1047001375.960512 diff from last 5.005874
l2Accept 7.133007
l2Process 6.858945
evt 34407 token 1670
+++++++++++++++++++++++ l1 1047001521.012963 diff from last 145.052451
l2Accept 4.740000
l2Process 0.275970
evt 37618 token 781
+++++++++++++++++++++++ l1 1047001586.097787 diff from last 65.084824
l2Accept 2.403021
l2Process 0.279903
evt 38904 token 2060
+++++++++++++++++++++++ l1 1047001612.431145 diff from last 26.333358
l2Accept 2.142072
l2Process 0.270963
evt 42012 token 985
+++++++++++++++++++++++ l1 1047001676.231965 diff from last 63.800820
l2Accept 4.690051
l2Process 0.270963
evt 42989 token 2057
+++++++++++++++++++++++ l1 1047001696.234687 diff from last 20.002722
l2Accept 5.028009
l2Process 0.324965
evt 50781 token 1677
+++++++++++++++++++++++ l1 1047001856.531031 diff from last 160.296344
l2Accept 11.088014
l2Process 1.291990
evt 54139 token 813
+++++++++++++++++++++++ l1 1047001926.155229 diff from last 69.624198
l2Accept 2.096057
l2Process 1.327991
evt 56580 token 3289
+++++++++++++++++++++++ l1 1047001976.752979 diff from last 50.597750
l2Accept 7.080913
l2Process 1.163006
evt 67893 token 2387
+++++++++++++++++++++++ l1 1047002212.024108 diff from last 235.271129
l2Accept 3.724933
l2Process 1.330972
evt 72411 token 2817
+++++++++++++++++++++++ l1 1047002307.076830 diff from last 95.052722
l2Accept 2.484918
l2Process 3.592014
evt 73820 token 125
+++++++++++++++++++++++ l1 1047002337.072601 diff from last 29.995771
l2Accept 3.444076
l2Process 1.204967
evt 74753 token 1062
+++++++++++++++++++++++ l1 1047002357.085679 diff from last 20.013078
l2Accept 4.988909
l2Process 0.295997
evt 76149 token 2469
+++++++++++++++++++++++ l1 1047002387.082551 diff from last 29.996872
l2Accept 5.053043
l2Process 0.278950
evt 78749 token 935
+++++++++++++++++++++++ l1 1047002442.094000 diff from last 55.011449
l2Accept 4.412055
l2Process 0.620961
evt 80878 token 3106
+++++++++++++++++++++++ l1 1047002487.143729 diff from last 45.049729
l2Accept 3.643990
l2Process 1.247048
evt 80907 token 3125
+++++++++++++++++++++++ l1 1047002487.751876 diff from last 0.608147
l2Accept 2.264977
l2Process 0.262976
evt 84646 token 2773
+++++++++++++++++++++++ l1 1047002567.174757 diff from last 79.422881
l2Accept 5.028963
l2Process 0.280023
evt 87572 token 1611
+++++++++++++++++++++++ l1 1047002629.436782 diff from last 62.262025
l2Accept 2.159953
l2Process 0.280023
evt 87705 token 1639
+++++++++++++++++++++++ l1 1047002632.316353 diff from last 2.879571
l2Accept 2.382040
l2Process 0.272989
evt 90501 token 435
+++++++++++++++++++++++ l1 1047002692.380629 diff from last 60.064276
l2Accept 7.784009
l2Process 0.295043
evt 93065 token 3009
+++++++++++++++++++++++ l1 1047002747.490286 diff from last 55.109657
l2Accept 3.733039
l2Process 1.327991
evt 94001 token 3945
l2Accept 0.881076
l2Process 5.591989
evt 94228 token 60
+++++++++++++++++++++++ l1 1047002772.551485 diff from last 25.061199
l2Accept 2.861023
l2Process 1.304030
evt 94699 token 486
+++++++++++++++++++++++ l1 1047002782.574804 diff from last 10.023319
l2Accept 4.778028
l2Process 1.301050
evt 96103 token 1945
+++++++++++++++++++++++ l1 1047002812.614797 diff from last 30.039993
l2Accept 3.684998
l2Process 2.372980
evt 97000 token 2838
+++++++++++++++++++++++ l1 1047002831.799198 diff from last 19.184401
l2Accept 2.225995
l2Process 0.276923
evt 97040 token 2890
+++++++++++++++++++++++ l1 1047002832.642185 diff from last 0.842987
l2Accept 2.861023
l2Process 1.294971
Frank Geurts wrote:
> Zoran Milosevich wrote:
> > i'm a little confused. this message was sent today, and talks about
runs from
> > last night, yet gives log information from the previous night.
>
> no confusion here: the message is sent today, correct. What triggered
> going through the det.log files was an alleged tof problem last night
> (turned out to be L3) and the excerpt from the log file is from Thursday
> March 6 at 8h34 AM and concerns run 4065011 ...
>
> > do you see problems
> > after about run 4065050? if so, please let me know which run number.
>
> yes, i can see them for runs after 4065050 as well. Below is a dump of
> run 4065052 (the first physics run after pedestal runs 50 and 51). This
> remains much like this for all the following runs.
>
>
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:37 EDT