Re: long lines and slowness (common when viewing style sheets)

"Sebastian Geerken" <[email protected]>
Newsgroups gmane.comp.web.dillo.devel
Message-ID <[email protected]>
On Di, Mai 26, 2015, eocene wrote:
> 
> Now that everyone likes to send their style sheets as one big long line,
> like 250k long, viewing them in dillo is slow.
> 
> gprof says
>   %   cumulative   self              self     total           
>  time   seconds   seconds    calls   s/call   s/call  name    
>  32.47      1.88     1.88 189407242     0.00     0.00  lout::misc::NotSoSimpleVector<dw::Textblock::Word>::getRef(int) const
>  29.36      3.58     1.70 187437456     0.00     0.00  dw::Textblock::BadnessAndPenalty::lineCanBeBroken(int)
>  28.15      5.21     1.63    29345     0.00     0.00  dw::Textblock::wrapWordInFlow(int, bool)
> 
> and I wonder whether any optimizations are possible.

Yes, I know this bug (you sent it me some time ago), and it is on my
todo list.

Since this occured first with hyphenation (or rather per-line
optimization), there is certainly a way to optimize it. A vague guess
is that it has to do with the iteration over the line to find the best
break point.

(BTW: the functionality used for plain text could also be provided by
a new widget which is much simpler than Textblock.)

Sebastian

_______________________________________________
Dillo-dev mailing list
[email protected]
http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev
signature.asc (application/pgp-signature, 473 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVZM6YAAoJEAw7+YHB+ZL6FDQIAJBQmI/s0dO3NAKEbRUkFg3f
W2Gr/i50r/cdo/PS5qs3Cagc46ZzwT/3e0CZNWUXSAY2XKNY37CZdSRrDmh3v6id
oDAUq5Xuo+RYdJUHDUJELDsRaokeXgCH5HlUIvh8gO2b2bQkt34n0qnMVO41BCLp
jDTT2fzaIQ+FLDwKhUfehbXhIl0AJIXmaxunOD3pYHFjapzGpS2mcTE1k9JJ7p6w
8HdtWPO7oQtN5XHIuMrQcewVI5W1A9SN+h5lBr0rSEgrJW7Dc4tFvoubvwV64RAa
Gq4zFfMrKNqc0SaNwf4Pnsz2a8DpP0LAUmeH409fgc0x1JxBJcOyn1or3XsJGGY=
=RdaL
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.