Gleipnir/jet
4
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Add wiki Generator page.

Browse source
This commit is contained in:
go-jet 2019-06-27 14:31:57 +02:00
parent b3ec1139b5
commit 3516d2861c
5 changed files with 298 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -447,8 +447,8 @@ In those cases web server handler execution time is directly proportional to lat
This is not such a big problem if handler calls database couple of times, but what if web server is using ORM to retrieve all data from database.
ORM usually access the database once for every object needed.
Now lets say latency is 30ms and there are 100 different objects required from the database. This handler will last 3s !!!.
With Jet, handler time lost on latency between server and database is constant(because we can write complex query and return result in one database call),
and handler execution will be proportional to number or rows returned from database.
With Jet, handler time lost on latency between server and database is constant. Because we can write complex query and
return result in one database call. Handler execution will be proportional to number or rows returned from database.
ORM example replaced with jet will take just 30ms + 'result scan time' = 31ms (rough estimate).
With Jet you can even join the whole database and store the whole structured result in in one query call.