Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / faster-cpython/ideas issues and pull requests
#701 - Communication about faster-cpython after 3.13 release?
Issue -
State: open - Opened by paugier about 2 months ago
- 1 comment
#700 - Embedded and virtual reference counts
Issue -
State: open - Opened by markshannon about 2 months ago
#699 - vectorcall kwnames C array
Issue -
State: open - Opened by dg-pb 2 months ago
#698 - Expand the tier 2 instruction format to 2 operands
Issue -
State: open - Opened by Fidget-Spinner 2 months ago
- 1 comment
#693 - Candidate-root based cycle GC
Issue -
State: open - Opened by markshannon 4 months ago
#684 - Use UTF-8 internally for strings.
Issue -
State: open - Opened by markshannon 6 months ago
- 17 comments
#545 - Handling "tuple/any/all comprehensions" in the compiler.
Issue -
State: open - Opened by markshannon almost 2 years ago
- 6 comments
#100 - Specialize BINARY_SUBTRACT
Issue -
State: closed - Opened by corona10 about 3 years ago
- 4 comments
#99 - Consider what programs to run during PGO
Issue -
State: closed - Opened by ammaraskar about 3 years ago
- 14 comments
#98 - Speed up "from X import A; from X import B; from X import C; ..."
Issue -
State: closed - Opened by gvanrossum about 3 years ago
- 6 comments
#97 - Compile with `-O2` instead of `-O3`
Issue -
State: closed - Opened by brandtbucher about 3 years ago
- 4 comments
#96 - Reorder instruction cases in `_PyEval_EvalFrameDefault`
Issue -
State: closed - Opened by brandtbucher about 3 years ago
- 12 comments
#95 - Align quickened code to cache line boundaries
Issue -
State: closed - Opened by brandtbucher about 3 years ago
- 10 comments
#94 - Worry about bugs that hard to find
Issue -
State: closed - Opened by ghost about 3 years ago
- 5 comments
#93 - 5x speedups without JIT compiler + portability...
Issue -
State: closed - Opened by sbrunthaler about 3 years ago
- 10 comments
#92 - Merge co_names and co_consts into a single array.
Issue -
State: closed - Opened by markshannon about 3 years ago
- 13 comments
#91 - Maybe rewrite small functions like `map` in Python.
Issue -
State: closed - Opened by markshannon about 3 years ago
- 3 comments
#90 - Daemon mode to speed up startup?
Issue -
State: closed - Opened by gvanrossum about 3 years ago
- 4 comments
#89 - Use a principled, and consistent, implementation of freelists.
Issue -
State: closed - Opened by markshannon about 3 years ago
- 11 comments
#88 - Faster hash function
Issue -
State: closed - Opened by itamarst about 3 years ago
- 14 comments
#87 - Overhead from having more bytecodes
Issue -
State: closed - Opened by kmod about 3 years ago
- 8 comments
#86 - Faster startup -- Share code objects from memory-mapped file
Issue -
State: closed - Opened by yuleil about 3 years ago
- 9 comments
#85 - Lazily create code object co_code attribute.
Issue -
State: closed - Opened by markshannon about 3 years ago
- 3 comments
#84 - Faster startup -- Experiment E -- "deep-freeze" code objects as static C data structures
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 25 comments
#83 - Faster startup -- Experiment D -- streamline code objects
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 5 comments
#82 - Freeze/link all stdlib modules imported during startup.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 16 comments
Labels: investigate, Epic
#81 - Specialize LOAD_METHOD
Issue -
State: closed - Opened by Fidget-Spinner over 3 years ago
- 10 comments
#80 - Regular object layout
Issue -
State: closed - Opened by markshannon over 3 years ago
- 12 comments
#79 - Use member non-pointer declarations in Py*State structs instead of heap-allocated pointers.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 6 comments
#78 - Freeze initialized runtime state for use in subsequent executions.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 3 comments
Labels: investigate
#77 - Changes in the compiler and dictionary to make key sharing in classes more effective.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 1 comment
#76 - [profiling] Gather low-level profile data for the various benchmarks.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 1 comment
#75 - [profiling] Profile/analyze runtime startup (and shutdown).
Issue -
State: open - Opened by ericsnowcurrently over 3 years ago
- 18 comments
#74 - Specializations
Issue -
State: closed - Opened by markshannon over 3 years ago
- 16 comments
Labels: Epic, epic-specialization
#73 - Specialize BINARY_ADD and INPLACE_ADD
Issue -
State: closed - Opened by markshannon over 3 years ago
- 2 comments
#72 - Compact layout of Plain Python Objects
Issue -
State: closed - Opened by markshannon over 3 years ago
- 15 comments
Labels: epic-compact-objects, 3.13
#71 - Hybrid RC and mark+sweep GC
Issue -
State: closed - Opened by nascheme over 3 years ago
- 6 comments
#70 - Compact object headers
Issue -
State: closed - Opened by markshannon over 3 years ago
- 9 comments
#69 - Object layout
Issue -
State: closed - Opened by markshannon over 3 years ago
- 6 comments
#68 - Explain these POP_JUMP_IF_FALSE/POP_JUMP_IF_TRUE timings
Issue -
State: closed - Opened by iritkatriel over 3 years ago
- 4 comments
#67 - Consider FOR_ITER family for specialization?
Issue -
State: closed - Opened by Fidget-Spinner over 3 years ago
- 29 comments
Labels: epic-specialization
#66 - Faster startup -- Experiment C -- lazy unmarshalling
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 159 comments
#65 - Faster startup -- Experiment B -- streamline and tweak
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 62 comments
#64 - Faster startup -- Experiment A
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 4 comments
#63 - Implement specialization for SUBSCRIPT ops
Issue -
State: closed - Opened by iritkatriel over 3 years ago
- 2 comments
#62 - Replace certain control-flow exceptions with GOTO
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 13 comments
#61 - bpo-33092: The bytecode for f-string formatting is inefficient.
Issue -
State: closed - Opened by iritkatriel over 3 years ago
- 1 comment
#60 - Pull pyston benchmarks into pyperformance.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 25 comments
#59 - Implement BINARY_SUBSCR specialization "family" for PEP 659 adaptive interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 7 comments
#58 - Move GC to a separate thread
Issue -
State: closed - Opened by iritkatriel over 3 years ago
- 33 comments
#57 - Improve tuple/list index-by-long speed
Issue -
State: closed - Opened by heeres over 3 years ago
- 3 comments
#56 - Document the instruction format.
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 5 comments
#55 - Improve generated code for some cases
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 12 comments
#54 - Implement CALL_FUNCTION specialization "family" for PEP 659 adaptive interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 24 comments
#53 - Implement STORE_ATTR specialization "family" for PEP 659 adaptive interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 2 comments
#52 - Port LOAD_ATTR from old opcache to PEP 659 adaptive interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 4 comments
#51 - Port LOAD_GLOBAL from old opcache to PEP 659 adaptive interpreter.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 1 comment
#50 - Is it possible to use SIMD instructions?
Issue -
State: closed - Opened by ghost over 3 years ago
- 5 comments
#49 - Speed up "create class"
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 4 comments
#48 - Official MSVC builds vs PGO, LTO, other compilers
Issue -
State: closed - Opened by lazka over 3 years ago
- 6 comments
#47 - If performance is the goal...
Issue -
State: closed - Opened by LifeIsStrange over 3 years ago
- 3 comments
#46 - [created by accident]
Issue -
State: closed - Opened by alejolp over 3 years ago
#45 - "Zero overhead" exception handling
Issue -
State: closed - Opened by markshannon over 3 years ago
- 2 comments
Labels: 3.11
#44 - Develop better tooling for static and dynamic analysis
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 2 comments
#43 - Move the data and control (block) stacks to thread and generator/coroutines
Issue -
State: closed - Opened by markshannon over 3 years ago
- 3 comments
Labels: 3.10
#42 - More efficient implementation of integers
Issue -
State: closed - Opened by markshannon over 3 years ago
- 20 comments
#41 - Handle boxing of cell variables in the bytecode.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 12 comments
Labels: 3.11
#40 - Plan for the coming 6-12 months and parallel workstreams
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 1 comment
Labels: Meta
#39 - Split YIELD_FROM into two
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 1 comment
#38 - Add bytecode to handle gen.send() corner cases
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 1 comment
Labels: 3.10
#37 - Offset cell variables from the base of locals
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 2 comments
Labels: 3.11
#36 - Combined instructions
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 5 comments
#35 - What can we do before 3.10 beta and the public announcement?
Issue -
State: closed - Opened by markshannon over 3 years ago
- 4 comments
#34 - Use instruction offset, not byte offset, in bytecodes.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 3 comments
Labels: 3.10
#33 - Improvements to the dispatching logic in the interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 7 comments
Labels: 3.11
#32 - Improve startup time.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 48 comments
#31 - Move the data and control (block) stacks on the thread and remove frame objects.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 8 comments
#30 - Dictionary modifications to enable optimizations.
Issue -
State: closed - Opened by markshannon over 3 years ago
- 17 comments
#29 - [profiling] Review the existing DXPAIRS instrumentation
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 6 comments
#28 - Adaptive, specializing interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 8 comments
#27 - Quickening interpreter
Issue -
State: closed - Opened by markshannon over 3 years ago
- 7 comments
#26 - Speculative specialization is the key optimization
Issue -
State: closed - Opened by markshannon over 3 years ago
- 2 comments
#25 - [profiling] Add profiling instrumentation centered on the eval loop
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 13 comments
Labels: deferred
#24 - Plan the public announcement of this project
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 3 comments
Labels: Meta
#23 - Create a small GitHub org through which we'll do the work
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 6 comments
Labels: Meta
#22 - Register-based VM
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 8 comments
#21 - (maybe) Add Tooling and Automation for Benchmarking/Profiling
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 3 comments
#20 - Add profiling support (and artifacts) to pyperformance.
Issue -
State: open - Opened by ericsnowcurrently over 3 years ago
- 1 comment
Labels: deferred, benchmarking
#19 - [benchmarking] Get a machine to run benchmarks on
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 8 comments
#18 - Incorporate azure-sdk / azure-cli into pyperformance suite
Issue -
State: open - Opened by ericsnowcurrently over 3 years ago
- 5 comments
Labels: blocked, benchmarking
#17 - Specialized eval loops for categories of functions
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 8 comments
Labels: deferred
#16 - Super-instructions
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 44 comments
#15 - Project management
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 1 comment
Labels: Meta
#14 - "immortal" objects
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 6 comments
#13 - High-level Perf Optimization Targets
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 2 comments
#12 - Profiling
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
- 12 comments
#11 - benchmarking (tooling, suites, workflow, etc.)
Issue -
State: closed - Opened by ericsnowcurrently over 3 years ago
#10 - Benchmarking
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 8 comments
#9 - Other people to invite
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 4 comments
Labels: Meta
#8 - A disassembler
Issue -
State: closed - Opened by gvanrossum over 3 years ago
- 4 comments