Ask Your Question

Revision history [back]

single threaded

I had to ingest a large pcapng file file. It took many minutes. I pulled up the CPU monitor and noted that only ONE thread was pulling CPU, and it was MAXED-OUT. (source was Sammy SSD; not the bottleneck...)

I used GPU-caps and took at look at what was running on the two GPUs. NOT wireshark...

Given the wide popularity of Wireshark (many many people world wide use this program), isn't it worth the effort to modernize the program to be multi-threaded (and/or to draw upon resources of the GPUs)?

(Well, I tried to upload a screen-grab of the CPU monitor, but I don't have enough points. I also don't have my old account. I've reported to Wireshark previously, and had an account, but found it gone, and had to create a new one...)

click to hide/show revision 2
None

single threaded

I had to ingest a large pcapng file file. It took many minutes. I pulled up the CPU monitor and noted that only ONE thread was pulling CPU, and it was MAXED-OUT. (source was Sammy SSD; not the bottleneck...)

I used GPU-caps and took at look at what was running on the two GPUs. NOT wireshark...

Given the wide popularity of Wireshark (many many people world wide use this program), isn't it worth the effort to modernize the program to be multi-threaded (and/or to draw upon resources of the GPUs)?

(Well, I tried to upload a screen-grab of the CPU monitor, but I don't have enough points. I also don't have my old account. I've reported to Wireshark previously, and had an account, but found it gone, and had to create a new one...)