I've currently got wireshark-win64-1.1.4-SVN-28266.exe installed and 4 more Gig RAM will be here Tuesday. Are there any specific tests anyone wants me to run once I have 8Gig RAM? The one feature I wish was in there is when wireshark runs out of memory it just stops loading the capture file at that point. It could say memory low, would you like to quit wireshark or work with only the 52% of the capture file that has been loaded so far. Also, click here to split the file in 2 parts. Just a thought...
Thanks for your Time!
Brian
--
CONFIDENTIAL OR PRIVILEGED: This communication contains information intended only for the use of the individuals to whom it is addressed and may contain information that is privileged, confidential, or exempt from other disclosure under applicable law. If you are not the intended recipient, you are notified that any disclosure, printing, copying, distribution, or use of the content is prohibited. If you have received this in error, please notify the sender immediately by telephone or by returning it by reply email and then permanently deleting the communication from your system. Thank you.
On Tue, Apr 28, 2009 at 1:17 PM, Guy Harris
<guy@xxxxxxxxxxxx> wrote:
On Apr 28, 2009, at 10:10 AM, Brian Daniel wrote:
> I want to take max advantage of my quad processor and RAM. Will the
> Windows-XP-Win64 build of WireShark take advantage of the additional
> RAM if I upgrade my Windows Vista 64-bit from 4Gig RAM to 8Gig RAM?
A 64-bit version of Wireshark will be able to have more than 4GB of
data in its address space if you have enough RAM (and possibly even if
you don't, if you have enough backing store - paging files and/or
paging partitions - although that means it could be paging stuff into
and out of main memory a lot). Wireshark will do so only if you try
to read in a file large enough to require it.
A 32-bit or 64-bit version of Wireshark will, on a machine with more
than 4GB of RAM and an operating system that supports that RAM as
general paging memory (rather than the specialized support offered by
32-bit versions of Windows), be able to, even if it doesn't have more
than 4GB of data in its address space, share that memory with more
programs or bigger programs, so, *if* you're running other stuff that
could compete with Wireshark for memory, and that competition is
happening and slowing Wireshark (and the other stuff) down, even a 32-
bit version of Wireshark could work better if you add more memory.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
