Ethereal-dev: Re: [Ethereal-dev] Re: [Ethereal-cvs] rev 16615: /trunk/image/: Makefile.nmake d

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Ulf Lamping <ulf.lamping@xxxxxx>
Date: Tue, 29 Nov 2005 19:45:20 +0100
Ethereal development <ethereal-dev@xxxxxxxxxxxx> schrieb am 29.11.05 14:42:22:
> 
> 
> You should see the painfully long startup time for captures on a P/166 MMX
> 64MB box I have.  It takes a long time for the UI to assemble itself, and
> that I expect.  But starting the capture takes nearly as long all over
> again, and that I do *not* expect.  95% of the code in that subprocess
> will never be touched, but it seems to make things slow anyway.

Well, when starting a capture, it's not only starting another instance of Ethereal (and using some memory and alike).

It's also calling all the init functions (GTK, dissectors, ...), loading plugins, ... so you can imagine that this *will* take some time even if the libs are already in memory.

Anyway, using a P166/64MB seems to be *very* low-level for an X program ...

> 
> Okay, this box is old and small.  But some current embedded systems don't
> have much memory and don't need a lot of CPU horsepower for their usual
> tasks.  I suspect that a minimal capture program would be very welcome
> on such hosts, and it wouldn't be unwelcome anywhere else.
> 

That was one of the reasons ...

Regards, ULFL
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193