StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. Waitress vs gevent

Waitress vs gevent

OverviewComparisonAlternatives

Overview

gevent
gevent
Stacks260
Followers52
Votes0
Waitress
Waitress
Stacks16
Followers58
Votes7
GitHub Stars1.5K
Forks182

Waitress vs gevent: What are the differences?

Introduction

In this article, we will discuss the key differences between Waitress and gevent, two popular Python servers. Markdown code will be used for easy integration into a website.

  1. Concurrency Model: Waitress is based on a threaded concurrency model, where each request is handled by a separate thread. On the other hand, gevent is built on an event-driven concurrency model using coroutines, making it lightweight and efficient.

  2. Performance: Waitress provides good performance, but it may not be as fast as gevent, especially when handling a large number of concurrent connections. Gevent's asynchronous architecture allows it to handle a higher number of requests efficiently and achieve better performance.

  3. Dependencies: Waitress has minimal external dependencies and can be easily installed without any complex setup. Gevent, however, requires libevent to be installed on the system and has additional dependencies, making the initial setup more involved.

  4. Compatibility: Waitress is compatible with both WSGI (Web Server Gateway Interface) and ASGI (Asynchronous Server Gateway Interface) applications, making it versatile and flexible. Whereas gevent is primarily designed for WSGI applications and may require additional configuration to work with ASGI applications.

  5. Community and Support: Waitress has a relatively larger community and better documentation, making it easier to find help and resources when needed. Gevent, although popular, has a smaller community and may require more effort to find support.

  6. Integration with Web Frameworks: Waitress has seamless integration with popular Python web frameworks like Flask and Django, allowing developers to easily deploy their applications. Gevent, on the other hand, may require additional configuration and specific handling to work with some web frameworks.

In summary, Waitress and gevent differ in their concurrency models, performance, dependencies, compatibility, community support, and integration with web frameworks. Choose Waitress if you need versatility and compatibility, while gevent is a great choice for high-performance and scalable applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

gevent
gevent
Waitress
Waitress

It is a coroutine -based Python networking library that uses greenlet to provide a high-level synchronous API on top of the libev or libuv event loop.

It is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.4+. It is also known to run on PyPy 1.6.0 on UNIX.

Fast event loop based on libev or libuv; Lightweight execution units based on greenlets; API that re-uses concepts from the Python standard library (for examples there are events and queues); Cooperative sockets with SSL support; Cooperative DNS queries performed through a threadpool, dnspython, or c-ares; Monkey patching utility to get 3rd party modules to become cooperative; TCP/UDP/HTTP servers; Subprocess support (through gevent.subprocess); Thread pools
Production-quality WSGI server ; Dont hang a thread up trying to send data to slow clients;Use self.logger to log socket errors instead of self.log_info (normalize); Remove pointless handle_error method from channel; Queue requests instead of tasks in a channel
Statistics
GitHub Stars
-
GitHub Stars
1.5K
GitHub Forks
-
GitHub Forks
182
Stacks
260
Stacks
16
Followers
52
Followers
58
Votes
0
Votes
7
Pros & Cons
Cons
  • 1
    Not native
Pros
  • 2
    Runs on Windows
  • 1
    Reliable
  • 1
    Light
  • 1
    Easy setup
  • 1
    Cross Platform
Integrations
Django
Django
Python
Python
Windows
Windows
Python
Python
Flask
Flask

What are some alternatives to gevent, Waitress?

NGINX

NGINX

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

lighttpd

lighttpd

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Swoole

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase