From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Help me getting started.
Date: Thu, 30 Dec 2010 17:31:43 +0200 [thread overview]
Message-ID: <1293722265-sup-2399@tilus.net> (raw)
In-Reply-To: <4D1321A2.9070206@lophus.org>
Jonas H., 2010-12-23 12:17:
> On 12/20/2010 02:57 PM, Tero Tilus wrote:
> > I've never had any problems with that. Not even with really lo-fi hw.
> > Could you try profiling if? (gem install ruby-prof, launch sup using
> > ruby-prof and do scrolling, preferably a lot of it and then exit)
>
> Results attached; the 'short' log is without lines that only consist of
> 0.0[012] 0.0[012] ... 0.0[012].
The biggest problem seems to be String#display_length with ruby
versions < 1.9.1. Manually calculating display lenght using
scan(/./u) is definitely not nice, but I don't know how could you make
it faster. Maybe caching calculated display_lengths?
Looks like I just haven't done enough scrolling to find that out. :-O
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-30 15:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:57 Jonas H.
2010-12-19 23:34 ` Ben Walton
2010-12-20 7:57 ` Tero Tilus
2010-12-20 13:39 ` Jonas H.
2010-12-20 18:24 ` Marc Hartstein
[not found] ` <4D0F5C5E.7030809@lophus.org>
2010-12-20 13:57 ` Tero Tilus
2010-12-23 10:17 ` Jonas H.
2010-12-30 13:14 ` Jonas H.
2010-12-30 15:31 ` Tero Tilus [this message]
2010-12-30 21:33 ` Tero Tilus
2010-12-30 23:09 ` Tero Tilus
2010-12-30 23:03 ` Tero Tilus
2010-12-30 23:37 ` Jonas H.
2010-12-31 0:45 ` Tero Tilus
2010-12-31 10:14 ` Jonas H.
2011-03-22 18:01 ` Jonas H.
2010-12-20 13:41 ` Mark Alexander
2010-12-20 14:10 ` Shadowfirebird
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1293722265-sup-2399@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox