--===============2130090904==
Content-Type: multipart/signed;
  boundary="nextPart13479071.j0VuL6NOkn";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart13479071.j0VuL6NOkn
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le Lundi 14 Novembre 2005 14:56, Koos Vriezen a =E9crit=A0:
> On Mon, Nov 14, 2005 at 01:44:14PM +0100, Olivier Goffart wrote:
>
> > As result i obtain
> >
> > normalized: 2469ms
> > usual: 5323ms    ratio: 2.15593
>
> 2.6ms/connect still doesn't say much actually, does sound quite slow
> (but maybe you ran it on a 66 MHz ARM CPU :)

5323/(20000*3) =3D less than 0.1 ms  per connect/disconnect pair
It was on a 1,8Ghz Pentium M

Yes, it's quite few.  that is why i ask if it would be interesting to write=
 a=20
script that normalize the signature of signals in the code.

I don't know how many signals/slots are connected at kde start, but it shou=
ld=20
be much.
is gaining 0.02ms per connection interesting enough ?

--nextPart13479071.j0VuL6NOkn
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDeKHjz58lY8jWrL0RAmPmAJ4722ODFSX2VVb7qGb/E5tvur/6RwCfVOHz
qE1honsM7Ehp8aE7AXCI5Io=
=R/aO
-----END PGP SIGNATURE-----

--nextPart13479071.j0VuL6NOkn--

--===============2130090904==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-optimize mailing list
Kde-optimize@kde.org
https://mail.kde.org/mailman/listinfo/kde-optimize

--===============2130090904==--