Result for 23A0C47D5940386334CBF3CD707627625B3DE32C

Query result

Key Value
FileName./usr/share/doc/packages/ruby2.6-rubygem-puma-1_6/COPYING
FileSize57
MD5E6E680205DD90837EA976775E3439AE7
SHA-123A0C47D5940386334CBF3CD707627625B3DE32C
SHA-2562851F8B0C893A4079A9E5E43086772BBF31EDD33A49C579DC14049DF02B82D14
SSDEEP3:gC63cZA21+rKupMsri:dzmLpM5
TLSHT1459002B103B230E5780048947C1DEE4657440C0937153F05215E66280108615609B0C8
hashlookup:parent-total7
hashlookup:trust85

Network graph view

Parents (Total: 7)

The searched file hash is included in 7 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5AA6F408DA0AE6C67F2C72C340A6FB352
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageRelease3.5
PackageVersion1.6.3
SHA-1BB473CF75B100EBEB37B2FA5577093C1B3770361
SHA-256941B20BABEF1D9E320904E937C32C5B6877A11413292C1A51153D473C4BD125C
Key Value
MD5CC18580DB7CF6A6B7A96F9D802E8077A
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageRelease3.50
PackageVersion1.6.3
SHA-12D01DBD3964A4B8037550F0E13A1F1DD437FB998
SHA-25662D0CFBC0EC2B5114EF8E90B6F8B3EBD8466B78B679190B0343BADE954612496
Key Value
MD5B835C2E3729A9D8223ACB09A4A0FD1F3
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageReleaselp153.3.22
PackageVersion1.6.3
SHA-111B8567316A9A47E3E91ED85F7C9AA110232F8D9
SHA-25679424A1374CB35C508B9A8551B2AB3E56770648EDB664289D9479E2585ED8EC7
Key Value
MD5768D163FA79990FDD1326B3FC8E4FC22
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageRelease3.36
PackageVersion1.6.3
SHA-10423BF61E2BEE582CEF203F5A7E6145E19D812EC
SHA-2568815FA04611B2DC8B0563863C119B2BA363E85A80EF79C77DE86D8BA803B5380
Key Value
MD5D8324E451241583D3CCC4F8860782F2B
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageReleaselp152.3.11
PackageVersion1.6.3
SHA-1BA9314802CC301F2BED5FF1EEEE610FAA2FE416A
SHA-256ED2E7D058D38805E8043B8D722312439F7F2BE1EEDC8D44F33A17FE3439D660D
Key Value
MD589162B1DB46AF5CB59E81DE13EA87FF2
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageReleaselp154.3.3
PackageVersion1.6.3
SHA-1FB24EFBAF1825D994D18996E708B3163A92C67ED
SHA-256DD917D4B17CE5B4CC07F371BD1129ABBDA4CFBA579835393E1CA060684A25EBD
Key Value
MD560BE8C9EA0A79C1E23E61FDCB9CBCF43
PackageArchx86_64
PackageDescriptionPuma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageNameruby2.6-rubygem-puma-1_6
PackageReleaselp151.3.8
PackageVersion1.6.3
SHA-1845C6A71E5195A3EA4070504FC4A09BE9CEF1198
SHA-256F8CF8A1AD7198FF7CBAC48D76BE9F9D706AE59452F35B0BF73363EC0DFE3EFB8