OpenResty 1.27.1.2 Released
- Version highlights
- Full Changelog
- Feedback
- Version highlights
- Full Changelog
- Feedback
← Back
Openresty
OpenResty 1.27.1.1 Released
- Version highlights
- Full Changelog
- Feedback
- Version highlights
- Full Changelog
- Feedback
OpenResty 1.25.3.1 Released
- Version highlights
- Full Changelog
- Feedback
- Version highlights
- Full Changelog
- Feedback
OpenResty 1.21.4.2 Released
- Version highlights
- Full Changelog
- Feedback
- Version highlights
- Full Changelog
- Feedback
How we solved a CPU bottleneck caused by Lua exceptions in a custom Kong plugin (using OpenResty XRay)
- The problem: high CPU usage in Kong servers
- The analysis & report
- The result: improved performance and reduced CPU usage
- The problem: high CPU usage in Kong servers
- The analysis & report
- The result: improved performance and reduced CPU usage
Memory and CPU usage statistics among Kong plugins online (using OpenResty XRay)
- CPU usage among all Kong plugins in a server process
- Memory usage among all Kong plugins in a server process
- Extra overhead for the servers
- CPU usage among all Kong plugins in a server process
- Memory usage among all Kong plugins in a server process
- Extra overhead for the servers
Troubleshooting the extra 200-ms request latency online
- The Problem
- The Analsysis Process
- Fully-automated analysis
- What is OpenResty XRay
- The Problem
- The Analsysis Process
- Fully-automated analysis
- What is OpenResty XRay
EdgeLang: A Powerful and Efficient Language for Gateway Logic
- Introduction to Edgelang
- Benefits of Edgelang
- Edgelang in Edge Admin
- Introduction to Edgelang
- Benefits of Edgelang
- Edgelang in Edge Admin
Pinpointing leaked Lua tables with OpenResty XRay's command-line tools
- How LuaJIT manages memory
- OpenResty XRay’s command-line tools
- An leaking example
- Analysis procedure
- lj-gco-ref analyzer
- Fully-automated analysis
- How LuaJIT manages memory
- OpenResty XRay’s command-line tools
- An leaking example
- Analysis procedure
- lj-gco-ref analyzer
- Fully-automated analysis
Real-Time Request Counting against Nginx Processes via YSQL
- How to install the run-ysql tool
- Count total requests served in real time
- Filter out specific requests
- Using YSQL in the Web Console
- True non-invasive tracing
- How to install the run-ysql tool
- Count total requests served in real time
- Filter out specific requests
- Using YSQL in the Web Console
- True non-invasive tracing
OpenResty 1.21.4.2 RC1 is out
- Source package
- Windows binary packages
- Version highlights
- Source package
- Windows binary packages
- Version highlights
When Lua IPC Pipes Block OpenResty or Nginx's Event Loops
- The Problem
- Analyses
- Solutions
- Results
- The Problem
- Analyses
- Solutions
- Results
Optimize Memory Fragmentation due to Huge Nginx Configuration
- Challenges
- Analyses
- Solutions
- Results
- Challenges
- Analyses
- Solutions
- Results
Tracing the Slowest PCRE Regular Expressions in OpenResty or Nginx Processes
- System Environment
- Narrowing Down the Culprit without Guessing
- Limiting the execution overhead of PCRE
- Non-Backtracking Regular Expression Engines
- Lua’s Builtin Patterns
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
- System Environment
- Narrowing Down the Culprit without Guessing
- Limiting the execution overhead of PCRE
- Non-Backtracking Regular Expression Engines
- Lua’s Builtin Patterns
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
Listing Loaded Lua Modules in OpenResty or Nginx Processes
- System Environment
- Names of Loaded Lua Modules
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
- System Environment
- Names of Loaded Lua Modules
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
Analyzing the Most CPU-Consuming Requests in OpenResty or Nginx
- System Environment
- CPU-Hottest Request Hostnames
- CPU-Hottest Request URIs
- Digging Deeper
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
- System Environment
- CPU-Hottest Request Hostnames
- CPU-Hottest Request URIs
- Digging Deeper
- Running Directly in the Web Console
- Tracing Applications inside Containers
- How The Tools are Implemented
- The Overhead of the Tools
OpenResty 1.19.9.1 released
- Version highlights
- Full Changelog
- Alpine 3.14 official release
- Version highlights
- Full Changelog
- Alpine 3.14 official release
OpenResty 1.19.9.1 RC1 is out
- Source package
- Windows binary packages
- Version highlights
- Source package
- Windows binary packages
- Version highlights
OpenResty 1.19.3.2 released
- Version highlights
- Full Change logs
- Version highlights
- Full Change logs
Official OpenResty Fedora 34 & Alpine 3.13 pkg repo
- Fedora 34
- Alpine 3.13
- Fedora 34
- Alpine 3.13
Official OpenResty Aarch64/ARM64 pkg repo
- Ubuntu 18.04/20.04
- Debian 9/10
- CentOS/RHEL 7/8，Fedora 32/33
- Ubuntu 18.04/20.04
- Debian 9/10
- CentOS/RHEL 7/8，Fedora 32/33
Introduction to Lua-Land CPU Flame Graphs
- What is a Flame Graph
- Simple Lua samples
- Complicated Lua applications
- Sampling overhead
- Safety
- Compatibility
- Other types of Lua-land Flame Graphs
- What is a Flame Graph
- Simple Lua samples
- Complicated Lua applications
- Sampling overhead
- Safety
- Compatibility
- Other types of Lua-land Flame Graphs
Memory Fragmentation in OpenResty and Nginx's Shared Memory Zones
- An empty zone
- Filling entries of similar sizes
- Deleting odd-numbered keys
- Deleting the keys in the first half
- Mitigating Fragmentation
- An empty zone
- Filling entries of similar sizes
- Deleting odd-numbered keys
- Deleting the keys in the first half
- Mitigating Fragmentation
How OpenResty and Nginx Shared Memory Zones Consume RAM
- Slabs and pages
- What is allocated is not what is paid for
- Fake Memory Leaks
- HUP reload
- Slabs and pages
- What is allocated is not what is paid for
- Fake Memory Leaks
- HUP reload
OpenResty 1.17.8.1 released
- OpenResty 1.17.8.1 released
- Full Changelog
- The Next Release
- OpenResty 1.17.8.1 released
- Full Changelog
- The Next Release
OpenResty 1.15.8.3 + OpenResty 1.17.8.1 RC1 released
- Full Changelog
- The Next Release
- Full Changelog
- The Next Release
How OpenResty and Nginx Allocate and Manage Memory
- On The System Level
- On The Application Level
- For Traditional Nginx Servers
- On The System Level
- On The Application Level
- For Traditional Nginx Servers
The LuaJIT GC64 Mode
- The Old Memory Limit
- When Hitting The Memory Limit
- The Memory Limit Is Per Process
- GC-Managed Memory
- Memory Allocated Outside GC
- Extending The x64 Mode to The 4 GB Limit
- The New GC64 Mode
- How to Enable The GC64 Mode
- Performance Impact
- Debugging and Profiling Tool Chains
- The Old Memory Limit
- When Hitting The Memory Limit
- The Memory Limit Is Per Process
- GC-Managed Memory
- Memory Allocated Outside GC
- Extending The x64 Mode to The 4 GB Limit
- The New GC64 Mode
- How to Enable The GC64 Mode
- Performance Impact
- Debugging and Profiling Tool Chains