ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-users: Re: [Wireshark-users] tshark memory

From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Wed, 20 Jan 2010 08:20:21 +0100

Build fom trunk.

Regards

Anders

 


Från: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] För Abhijit Bare
Skickat: den 20 januari 2010 05:57
Till: Community support list for Wireshark
Ämne: Re: [Wireshark-users] tshark memory

 

I am running wireshark 1.0.4 on SLES 10 on dual quadcore Xeon 3GHz with 16G memory. Tshark is using one full core.
Should I try latest version?

 

Thanks,

Abhijit

 

 

On Tue, Jan 19, 2010 at 2:40 PM, Anders Broman <a.broman@xxxxxxxxx> wrote:



-----Ursprungligt meddelande-----
Från: wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] För Guy Harris
Skickat: den 19 januari 2010 22:07
Till: Community support list for Wireshark
Ämne: Re: [Wireshark-users] tshark memory



On Jan 19, 2010, at 12:57 PM, Abhijit Bare wrote:

>> After 2 hours, my tshark process is using 3.6G RESIDENT memory and ~ 500G
>>VIRT memory in top output.
>
>To quote my reply:
>
>> When it reassembles fragmented/segmented/etc. packets, however, the
>>content of the reassembled packets *is* kept in memory.
>
>Other data structures that maintain state are also kept in memory.

What version on which platform? Some work to reduce memory usage and
Speed up filtering has been done in the development version you may want to
try that out. Although 2.5 TB is most probably to much depending on the
Type of traffic captured and if reassembly is turned of or on.
Regards
Anders

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users

mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe