litestack 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9f959b5e414b4190205ea516cf7acacf180714fd08f4fca9b90a3c84c2f9d594
-  data.tar.gz: 8350f9398d62a481fb656452cd3e4037237c83f292042f1b3db1e56445801a19
+  metadata.gz: c34bfdfaaa6a2472e132e05b1f80494a76d2311026c764b312a463f4f5cb2ee0
+  data.tar.gz: c27e887802afe1ee2f5c7e2c67aeb390fde3ef62adb6cec610e9e3f7af697753
 SHA512:
-  metadata.gz: 71c6fbd7f51fca6f8a55e86738fc5f28ae1a8452fe3a1a1f1b9cb6944850b71341c728f1eceb40a72b47a8e9f5ca38d07a83db7a7dbc740275bc4df335001032
-  data.tar.gz: 4fd49dd8559328728c9be9dbcf2740c9da22606501822877fccb16454b67aa0e7e5ecdc35a870752d9f02557c3e6d3397df6c68005a20543dd7b6dfd09873cda
+  metadata.gz: abd6ae7cd31c4988b911f147bcdd00f947fdda537993f854250b3d5c8b91bbb2d702faf0f73e07e6b54f4603253d90dd89ef80c41baab61cb313ccb9420d8e54
+  data.tar.gz: 58e3f6d9b443afc614d4254ace16c7ff3bd5bdfa1dbbfcfabf9e2eb8f69f57b7b1b15153ac59a7de91e303a305987b9aa92701f204140eea4e5ba4108a05725b

data/BENCHMARKS.md

@@ -16,7 +16,7 @@ This produces
 SELECT * FROM posts WHERE id = ?
 ```
 
-|Prcoess Count|ActiveRecord:PostgreSQL|ActiveRecord:litedb|Sequel:PostgreSQL|Sequel:litedb|
+|Prcoesses|AR:PG|AR:litedb|Sequel:PG|Sequel:litedb|
 |-:|-:|-:|-:|-:|
 |1|1.3K q/s|6.5K q/s|1.8K q/s|17.4K q/s|
 |2|2.6K q/s|13.9K q/s|3.5K q/s|33.2K q/s|
@@ -33,7 +33,7 @@ This produces
 SELECT * FROM posts WHERE user_id = ? LIMIT 5
 ```
 
-|Prcoess Count|ActiveRecord:PostgreSQL|ActiveRecord:litedb|Sequel:PostgreSQL|Sequel:litedb|
+|Prcoesses|AR:PG|AR:litedb|Sequel:PG|Sequel:litedb|
 |-:|-:|-:|-:|-:|
 |1|345 q/s|482 q/s|937 q/s|1.1K q/s|
 |2|751 q/s|848 q/s|1.3K q/s|2.3K q/s|
@@ -51,14 +51,14 @@ This produces
 Update posts SET updated_at = ? WHERE id = ?
 ```
 
-|Prcoess Count|ActiveRecord:PostgreSQL|ActiveRecord:litedb|Sequel:PostgreSQL|Sequel:litedb|
+|Prcoesses|AR:PG|AR:litedb|Sequel:PG|Sequel:litedb|
 |-:|-:|-:|-:|-:|
 |1|125 q/s|484 q/s|129 q/s|2.1K q/s|
 |2|265 q/s|576 q/s|333 q/s|2.5K q/s|
 |4|481 q/s|693 q/s|704 q/s|2.3K q/s|
 |8|898 q/s|748 q/s|1.2K q/s|2.4K q/s|
 
-It is clear the Litedb enjoys a clear advantage for reads and is very competitive for updates until many processes are relentlessly trying to write at the same time non stop.
+It is clear the Litedb enjoys a significant advantage for reads and is very competitive for updates until many processes are relentlessly trying to write at the same time non stop.
 For most applications, even with higher level of concurrency, Litedb will scale super well for reads and provide a very good baseline for writes.
 
 > ![litecache](https://github.com/oldmoe/litestack/blob/master/assets/litecache_logo_teal.png?raw=true)

data/lib/litestack/litecache.rb

@@ -228,6 +228,8 @@ class Litecache
               end
               @stmts[:pruner].execute!             
             end
+          rescue SQLite3::BusyException
+            retry
           rescue SQLite3::FullException
             @stmts[:extra_pruner].execute!(0.2)
           end

data/lib/litestack/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Litestack
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 end       

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: litestack
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Mohamed Hassan