I repeated the same thing with mrxvt 0.5.4 with --skipPages 1000.  The
result is worse in that it's just stuck (at least for five minutes)
without showing anything.

However, hopefully this result would shed a light on debugging.  I
wrapped the log file so each line has no more than 70 characters.

% wc xxx.log.col70
 126630  342183 7689058 xxx.log.col70

Note that it has about the same number of characters but a lot more
lines (with much shorter width).

% time cat xxx.log.col70
...
cat xxx.log.col70  0.00s user 0.12s system 2% cpu 4.283 total

It's absolutely fast.  So the question is, can you recognize where the
problem occurs?  Any place that may get slow when it handles long
lines?


On Wed, Aug 20, 2008 at 4:02 PM, Gautam Iyer <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 10:40:05AM -0400, Seung Jun wrote:
>
>> % wc xxx.log
>>   11914  285936 7632811 s1.director.outlier
>>
>> % time cat xxx.log
>> ...
>>
>> (mrxvt)
>> cat xxx.log  0.00s user 0.04s system 0% cpu 3:54.50 total
>>
>> (xterm)
>> cat xxx.log  0.00s user 0.05s system 0% cpu 1:03.51 total
>>
>> (gnome-terminal)
>> cat xxx.log  0.00s user 0.04s system 1% cpu 2.621 total
>>
>> Gnome-terminal is absolutely faster.  Note that mrxvt didn't use much
>> CPU.  Only its wall-clock time took long.  I guess it blocked on some
>> IO operations.
>
> Try it with mrxvt --skipPages 1000 (or even 10000). I think this is what
> gnome terminal uses.
>
>    $ wc /var/log/messages
>    74710  923641 6168908 /var/log/messages
>
>    $ time cat /var/log/messages # mrxvt with --skipPages 25
>    0.000u 0.186s 0:06.18 2.9%      0+0k 0+0io 0pf+0w
>
>    $ time cat /var/log/messages # mrxvt with --skipPages 100
>    0.003u 0.175s 0:01.16 14.6%     0+0k 0+0io 0pf+0w
>
>    $ time cat /var/log/messages # mrxvt with --skipPages 1000
>    0.001u 0.183s 0:00.82 21.9%     0+0k 0+0io 0pf+0w
>
>    $ time cat /var/log/messages # mrxvt with --skipPages 10000
>    0.000u 0.192s 0:00.66 28.7%     0+0k 0+0io 0pf+0w
>
> xterm took over two minutes, and I got bored waiting.
>
> GI
>
> PS: Like I said, make sure you use 0.5.4, with debugging disabled. Just
>    FYI, my machine is probably slower than yours. I use an Intel U7600
>    1.2gHz dual core CPU.
>
>    If not, perhaps some IO call is blocked on Solaris, and not on
>    Linux. This will be hard to track down since I don't have access to
>    a Solaris.
>
> --
> 100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
> 37. If my trusted lieutenant tells me my Legions of Terror are losing a
> battle, I will believe him. After all, he's my trusted lieutenant.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Materm-devel mailing list
> Materm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/materm-devel
> mrxvt home page: http://materm.sourceforge.net
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Materm-devel mailing list
Materm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/materm-devel
mrxvt home page: http://materm.sourceforge.net

Reply via email to