Skip to content

perf: pcap_ct extraction is about 2.3x slower on Python 3.15 than on 3.12-3.14 #2110

Closed

Description

@JarryShaw

The engine benchmark regenerated in #2109 shows pcap_ct taking 0.27 ms per packet on Python 3.15, against about 0.117 ms on 3.12–3.14. That is roughly 2.3× slower. All three passes agreed (0.2725, 0.2696 and 0.2702), so it is not noise. The other engines show no such jump.

Unknown: whether the cost is in pcap_ct itself, a ctypes change in 3.15, or the libpcap build in the python:3.15-slim-bookworm image (3.15.1).

Next step: profile PCAP_CT extraction on 3.14 and 3.15 in the benchmark images, compare cProfile call counts and cumulative times, and report where the extra time goes before proposing a fix.

Activity

  1. added
    perfPull requests that improve performance (perf: subject prefix)
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    on Oct 23, 2026
  2. added
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 23, 2026
  3. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 23, 2026
  4. added this to the PyPCAPKit v1.5 milestone on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    perfPull requests that improve performance (perf: subject prefix)

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions