Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

26.0.x: higher client CPU per call for `fetchone()` / `execute()` compared to 4.0.2

Abierto
  • ¿Algo no está bien?
#621 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
databases, performance

Línea de trabajo

Start by running the included repro_overhead.py against 4.0.2 and 26.0.1 in both thin and thick modes to confirm the fetchone() and execute() CPU gap while fetchmany() stays flat. Then compare how the two versions handle the per-row fetch path, since that is where the regression appears. Done means the per-call overhead is traced to a specific change and the numbers come back within a few percent of 4.0.2 in both modes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
  1. What versions are you using?
  • python-oracledb: 26.0.1, compared with 4.0.2 (stock PyPI wheels)
  • Oracle Database: 12.1.0.2.0
  • Oracle Client (Thick mode): 19.18.0.0.0
  • Python: 3.11.13
  • platform.platform: Linux-6.18.54.1-microsoft-standard-WSL2-x86_64-with-glibc2.35
  • sys.maxsize > 2**32: True
  1. Is it an error or a hang or a crash?

Neither: performance regression.

  1. What error(s) or behavior you are seeing?

fetchone() and execute() use more client CPU in 26.0.1 than in 4.0.2, in both Thin and Thick modes. fetchmany() is unchanged.

Client CPU time measured with the script below (seconds, average of two runs, each run being the median of 5):

Operation Mode 4.0.2 26.0.1 Change
fetchone() loop, 50k rows Thin 0.182 0.237 +31 %
fetchone() loop, 50k rows Thick 0.199 0.303 +52 %
2000 × (execute() + fetchone()) Thin 0.383 0.445 +16 %
2000 × (execute() + fetchone()) Thick 0.397 0.477 +20 %
fetchmany() scan, 50k rows Thin 0.169 0.179 +6 %
fetchmany() scan, 50k rows Thick 0.190 0.190 0 %
  1. Does your application call init_oracle_client()?

Both modes were measured (Thin and Thick).

  1. Include a runnable Python script that shows the problem.

No schema needed. Run once with each oracledb version:

ORA_USER=... ORA_PASSWORD=... ORA_DSN=host:port/service python repro_overhead.py thin
ORA_USER=... ORA_PASSWORD=... ORA_DSN=host:port/service python repro_overhead.py thick

import os
import statistics
import sys
import time

import oracledb

MODE = sys.argv[1] if len(sys.argv) > 1 else "thin"
ROWS = 50_000
N_EXEC = 2_000
REPEAT = 5

if MODE == "thick":
    oracledb.init_oracle_client()
oracledb.defaults.arraysize = 100
oracledb.defaults.prefetchrows = 101

conn = oracledb.connect(user=os.environ["ORA_USER"], password=os.environ["ORA_PASSWORD"],
                        dsn=os.environ["ORA_DSN"])

SCAN = f"""select level, level / 7, date '2026-01-01' + mod(level, 365), 'row_' || level
           from dual connect by level <= {ROWS}"""
ONE = "select :k, 'x' from dual"


def s1_fetchmany():
    with conn.cursor() as cur:
        cur.execute(SCAN)
        while cur.fetchmany():
            pass


def s2_execute_fetchone():
    with conn.cursor() as cur:
        for k in range(N_EXEC):
            cur.execute(ONE, k=k)
            cur.fetchone()


def s3_fetchone():
    with conn.cursor() as cur:
        cur.execute(SCAN)
        while cur.fetchone() is not None:
            pass


def cpu(fn):
    fn()                                    # warm-up
    samples = []
    for _ in range(REPEAT):
        c0 = time.process_time()
        fn()
        samples.append(time.process_time() - c0)
    return statistics.median(samples)


print("oracledb", oracledb.__version__, MODE)
print(f"fetchmany() scan of {ROWS} rows      : CPU {cpu(s1_fetchmany):.3f} s")
print(f"{N_EXEC} x (execute() + fetchone())  : CPU {cpu(s2_execute_fetchone):.3f} s")
print(f"fetchone() loop over {ROWS} rows     : CPU {cpu(s3_fetchone):.3f} s")
Lenguaje dominante
Python
Estrellas
455
Forks
119
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oracle/python-oracledb

Todos los issues de oracle/python-oracledb

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.