litestack 0.1.2 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 52b25ab2fd70ef40c8199c431e07638853915a131036abb52d1fef267a70cb13
-  data.tar.gz: 8f2bcf6c6fbc6d50e18664f74235b4242c79faa65317b1dcd7263ed0aa928161
+  metadata.gz: c34bfdfaaa6a2472e132e05b1f80494a76d2311026c764b312a463f4f5cb2ee0
+  data.tar.gz: c27e887802afe1ee2f5c7e2c67aeb390fde3ef62adb6cec610e9e3f7af697753
 SHA512:
-  metadata.gz: 1fa0edf72ea893a29f71f7398f685954243dd2cbd61080624ff91f49f389bf067c76cac491520f91c7f2470f568444d37eff0b72787d5f8418d6abbc869fd7c8
-  data.tar.gz: 75be276d72526cc1f68e204929822c8ba846b1d476d2d429de5c5e2e298df748b62de9d5c804912384ddec515505e6a42e0d9e09e4f27a3d27ff942f423a904c
+  metadata.gz: abd6ae7cd31c4988b911f147bcdd00f947fdda537993f854250b3d5c8b91bbb2d702faf0f73e07e6b54f4603253d90dd89ef80c41baab61cb313ccb9420d8e54
+  data.tar.gz: 58e3f6d9b443afc614d4254ace16c7ff3bd5bdfa1dbbfcfabf9e2eb8f69f57b7b1b15153ac59a7de91e303a305987b9aa92701f204140eea4e5ba4108a05725b

data/BENCHMARKS.md

@@ -11,9 +11,12 @@ These are not real life scenarios and I hope I will be able to produce some inte
 Post.find(id) #ActiveRecord
 Post[id] #Sequel
 ```
-This maps to "SELECT * FROM posts WHERE id = ?"
+This produces
+```sql
+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|
@@ -25,9 +28,12 @@ This maps to "SELECT * FROM posts WHERE id = ?"
 ```ruby
 Post.where(user_id: id).limit(5) # ActiveRecord and Sequel
 ```
-This maps to "SELECT * FROM posts WHERE user_id = ? LIMIT 5"
+This produces
+```sql
+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|
@@ -40,16 +46,19 @@ This maps to "SELECT * FROM posts WHERE user_id = ? LIMIT 5"
 Post.update(id, {updated_at: updated_at} # ActiveRecord
 Post[id].update({updated_at: updated_at}) # Sequel
 ```
-This maps to "Update posts SET updated_at = ? WHERE id = ?"
+This produces
+```sql
+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/README.md

@@ -53,7 +53,7 @@ litestack currently offers three main components
 
 > ![litedb](https://github.com/oldmoe/litestack/blob/master/assets/litedb_logo_teal.png?raw=true)
 
-litedb is a wrapper around SQLite3, offering a better default configuration that is tuned for concurrency and performance. Out of the box, litedb works seamlessly between multiple processes without database locking errors. lite db can be used in multiple ways, including:
+litedb is a wrapper around SQLite3, offering a better default configuration that is tuned for concurrency and performance. Out of the box, litedb works seamlessly between multiple processes without database locking errors. litedb can be used in multiple ways, including:
 
 #### Direct litedb usage
 
@@ -69,7 +69,7 @@ db.get_first_value("select count(*) from users") # => 1
 
 #### ActiveRecord
 
-litesd provides tight Rails/ActiveRecord integration and can be configured as follows
+litedb provides tight Rails/ActiveRecord integration and can be configured as follows
 
 In database.yml
 
@@ -162,7 +162,7 @@ The queues need to include a name and a priority (a number between 1 and 10) and
 
 ## Contributing
 
-Bug reports aree welcome on GitHub at https://github.com/oldmoe/litestack. Please note that this is not an open contribution project and that we don't accept pull requests.
+Bug reports are welcome on GitHub at https://github.com/oldmoe/litestack. Please note that this is not an open contribution project and that we don't accept pull requests.
 
 ## License
 

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.2"
+  VERSION = "0.1.4"
 end       

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: litestack
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.4
 platform: ruby
 authors:
 - Mohamed Hassan
@@ -65,9 +65,6 @@ files:
 - bench/bench_queue.rb
 - bench/bench_rails.rb
 - bench/bench_raw.rb
-- bench/queue.db
-- bench/queue.db-shm
-- bench/queue.db-wal
 - bench/rails_job.rb
 - bench/skjob.rb
 - bench/uljob.rb