Need advice about which tool to choose?Ask the StackShare community!

lighttpd

148
133
+ 1
27
Puma

840
265
+ 1
20
Add tool

Puma vs lighttpd: What are the differences?

Introduction

In web development, choosing the right web server is crucial to achieving optimal performance. Puma and lighttpd are two popular web servers that each have their own strengths and weaknesses. Understanding the key differences between them can help developers make an informed decision on which to use for their projects.

  1. Performance: Puma is known for its multi-threading capabilities, allowing it to handle a high volume of requests efficiently by utilizing all available CPU cores. On the other hand, lighttpd is known for its speed and low memory footprint, making it a better choice for serving static files or handling a large number of concurrent connections without consuming too many system resources.

  2. Configuration: Puma is typically used with Ruby on Rails applications and can be easily configured through the Rails application configuration files. In contrast, lighttpd has a more complex configuration setup that is done through its configuration file, making it less user-friendly for beginners but more customizable for advanced users looking to fine-tune their server settings.

  3. Flexibility: Puma is specifically designed to work well with Ruby applications and is commonly used in Ruby on Rails deployments. On the other hand, lighttpd is a more general-purpose web server that can be used with a wider variety of programming languages and frameworks, making it a versatile choice for different types of projects.

  4. Logging and Monitoring: Puma provides detailed logging capabilities that allow developers to monitor and analyze server performance and troubleshoot issues effectively. Lighttpd also offers logging functionality but may require additional tools or configurations to achieve the same level of detailed monitoring as Puma.

  5. Community Support: Puma has a strong community of Ruby on Rails developers who actively contribute to its development and provide support through forums, documentation, and online resources. Lighttpd also has a dedicated user base, but it may not have as extensive community support as Puma, particularly in the context of Ruby on Rails.

  6. Security Features: Lighttpd is known for its robust security features, including support for SSL/TLS encryption, chroot() function to sandbox processes, and various security modules that can enhance server security. Puma, while not lacking in security features, may not have the same level of out-of-the-box security configurations as lighttpd.

In Summary, understanding the key differences between Puma and lighttpd, such as performance, configuration, flexibility, logging and monitoring, community support, and security features, can help developers make an informed decision on which web server to use for their specific web development projects.

Advice on lighttpd and Puma
Mark Ndungu
Software Developer at Nouveta · | 4 upvotes · 37.7K views
Needs advice
on
PumaPuma
and
UnicornUnicorn

I have an integration service that pulls data from third party systems saves it and returns it to the user of the service. We can pull large data sets with the service and response JSON can go up to 5MB with gzip compression. I currently use Rails 6 and Ruby 2.7.2 and Puma web server. Slow clients tend to prevent other users from accessing the system. Am considering a switch to Unicorn.

See more
Replies (1)
Recommends
on
PumaPuma

Consider trying to use puma workers first. puma -w basically. That will launch multiple puma processes to manage the requests, like unicorn, but also run threads within those processes. You can turn the number of workers and number of threads to find the right memory footprint / request per second balance.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of lighttpd
Pros of Puma
  • 7
    Lightweight
  • 6
    Easy setup
  • 2
    Virtal hosting
  • 2
    Simplicity
  • 2
    Full featured
  • 2
    Proxy
  • 2
    Open source
  • 1
    Available modules
  • 1
    Fast
  • 1
    Security
  • 1
    Ssl support
  • 4
    Free
  • 3
    Convenient
  • 3
    Easy
  • 2
    Multithreaded
  • 2
    Consumes less memory than Unicorn
  • 2
    Default Rails server
  • 2
    First-class support for WebSockets
  • 1
    Lightweight
  • 1
    Fast

Sign up to add or upvote prosMake informed product decisions

Cons of lighttpd
Cons of Puma
    Be the first to leave a con
    • 0
      Uses `select` (limited client count)

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is 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.

    What is Puma?

    Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention lighttpd and Puma as a desired skillset
    What companies use lighttpd?
    What companies use Puma?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with lighttpd?
    What tools integrate with Puma?
      No integrations found

      Blog Posts

      What are some alternatives to lighttpd and Puma?
      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.
      LiteSpeed
      It is a drop-in Apache replacement and the leading high-performance, high-scalability server. You can replace your existing Apache server with it without changing your configuration or operating system details. As a drop-in replacement, it allows you to quickly eliminate Apache bottlenecks in 15 minutes with zero downtime.
      Caddy
      Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.
      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.
      Amazon EC2
      It is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers.
      See all alternatives