[Regression]: evaluate() with larger results ~40% slower since 1.65

Ouverte
#3,362 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
62/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
python
Domaine
performance

Piste de recherche

Start in protocol/validator_primitives.py, reading t_object and the t_optional helper, and trace where SerializedValue's schema keys are iterated. Before editing, run the issue's page.evaluate benchmark script to record a baseline, then re-run it after skipping the optional-key validators when a key is absent. Also run the protocol validator tests in tests/ (the suite that round-trips validated messages) to confirm malformed messages are still rejected. Done means the benchmark is back near 1.30s with unchanged validation behaviour, including for events and initializers.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Last Good Version

1.64.0

First Bad Version

1.65.0

Steps to reproduce

evaluate() with a medium-sized result got about 40% slower:

import time
from playwright.sync_api import sync_playwright

JS = "Array.from({length: 200}, (_, i) => ({id: i, name: 'item ' + i, price: i * 1.5, url: 'https://example.com/' + i, tags: ['a', 'b']}))"

with sync_playwright() as p:
    page = p.chromium.launch().new_page()
    page.evaluate(JS)
    best = 1e9
    for _ in range(3):
        start = time.perf_counter()
        for _ in range(300):
            page.evaluate(JS)
        best = min(best, time.perf_counter() - start)
    print(f"{best:.2f}s")
Expected behavior

1.64.0: 1.30s

Actual behavior

1.65.2: 1.84s

Additional context

cProfile points at the protocol validator: the t_object validator in protocol/validator_primitives.py is about 60% of the profiled time. For every object node it calls the validator of every key in the schema, and SerializedValue has ~15 optional keys, so most calls are t_optional(None) for keys that aren't there. It also calls context.is_under_test() once per node.

Skipping the call when the key is absent and the validator is a t_optional (the result is None in that case anyway) brings the script above to 1.47s in my test, same output. Validated messages also include every event and initializer, so it's not only evaluate.

Environment
- Operating System: macOS 27.2
- CPU: arm64
- Browser: Chromium
- Python Version: 3.14
- Other info:
Langage dominant
Python
Étoiles
15.1k
Forks
1.3k
Merge moyen
6 h 16 min
PR mergées (30 j)
53

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/playwright-python

Toutes les issues de microsoft/playwright-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.