I use ddb in my project. Updated my project to vibe.d v0.8.3 then sql query is very slow down. what can I do?
dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.2
====>> Working Time: 300 msecs . 300622 usecs . 300622200 nsecs -- 0.3 seconds
dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.3
====>> Working Time: 29727 msecs . 29727536 usecs . 29727536200 nsecs -- 29.727 seconds
On Thu, 15 Mar 2018 06:20:43 GMT, zafer wrote:
I use ddb in my project. Updated my project to vibe.d v0.8.3 then sql query is very slow down. what can I do?
dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.2 ====>> Working Time: 300 msecs . 300622 usecs . 300622200 nsecs -- 0.3 seconds dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.3 ====>> Working Time: 29727 msecs . 29727536 usecs . 29727536200 nsecs -- 29.727 seconds
I've tagged vibe-core 1.4.1-beta.1 and eventcore 0.8.33 with a number of stability fixes. Can you check if the slowdown still occurs? If yes, is multi-threading involved in the app and is DNS used for the requests?
I am sorry. I used ddb and still very slow. I don't use multi-thread or DNS.
I changed the database layer at the weekend. No longer I use dpq and dpq speed is well.
On Sun, 18 Mar 2018 21:18:44 GMT, Sönke Ludwig wrote:
On Thu, 15 Mar 2018 06:20:43 GMT, zafer wrote:
I use ddb in my project. Updated my project to vibe.d v0.8.3 then sql query is very slow down. what can I do?
dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.2 ====>> Working Time: 300 msecs . 300622 usecs . 300622200 nsecs -- 0.3 seconds dmd 2.078.3 -- dub 1.7.2 -- vibe.d 0.8.3 ====>> Working Time: 29727 msecs . 29727536 usecs . 29727536200 nsecs -- 29.727 secondsI've tagged vibe-core 1.4.1-beta.1 and eventcore 0.8.33 with a number of stability fixes. Can you check if the slowdown still occurs? If yes, is multi-threading involved in the app and is DNS used for the requests?
