Look into allowing SYNC command in the initial connection #35

New issue

Closed

opened 2018-08-28 00:37:24 +00:00 by jamie · 4 comments

jamie commented

2018-08-28 00:37:24 +00:00

(Migrated from git.hazaar.io)

Now that we've enabled Warlock as a KV storage database, speed is an issue. While the KV lookups are insanely fast because you know, it's in-memory and stuff.

The slow part is the initial connection. I will need to profile it, but I have a feeling it is related to the WebSocket negotiation and then having to issue the SYNC command. If I can remove the requirement for the SYNC command and add the auth/admin key stuff to the initial WebSocket request I should be able to shave quite a few milliseconds off the setup time.

Now that we've enabled Warlock as a KV storage database, speed is an issue. While the KV lookups are insanely fast because you know, it's in-memory and stuff. The slow part is the initial connection. I will need to profile it, but I have a feeling it is related to the WebSocket negotiation and then having to issue the SYNC command. If I can remove the requirement for the SYNC command and add the auth/admin key stuff to the initial WebSocket request I should be able to shave quite a few milliseconds off the setup time.

jamie commented

2018-08-28 21:55:19 +00:00

(Migrated from git.hazaar.io)

created branch 35-look-into-allowing-sync-command-in-the-initial-connection

created branch [`35-look-into-allowing-sync-command-in-the-initial-connection`](https://git.hazaarlabs.com/hazaar/hazaar-warlock/compare/master...35-look-into-allowing-sync-command-in-the-initial-connection)

jamie commented

2018-08-28 21:55:20 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !14