[BOT-API] Build executable binary

[4TT1L4]

Problem:

The Bot API Server is started using cabal run. This is not optimal, since cabal needs to look up some dependencies on every startup:

======[geniusyield-server]======
Startup checks....
SERVER_CONFIG is set and contains a valid YAML document.
====================================
Replace placeholders....
[OK] Done. Replaced placeholders.
+ cabal run geniusyield-server -- serve
====================================
Starting geniusyield-server...
Warning: Requested index-state 2023-06-06T00:00:00Z is newer than
'hackage.haskell.org'! Falling back to older state (2023-06-05T23:38:20Z).
Resolving dependencies...

The process to resolve dependencies on startup takes way to long, adding 20-30 seconds to the startup time.

Solution:

• Build an executable binary and start this instead of using cabal run to spin up the server.

[4TT1L4]

@sourabhxyz Could you please change the cabal config to provide an executable binary?

[sourabhxyz]

@4TT1L4 There shouldn't be an overhead if source files have not changed. The delay that you are seeing is likely due to the time it requires to initialise the Atlas's blockchain provider which in general takes ~30 seconds.

[4TT1L4]

Could you please add a log message when the initialization starts and finished? Otherwise it is not really possible to tell where the time goes.

I am also not sure if we should be "resolving dependencies" in production. I still think that we should build a binary and distribute this.

cabal run is designed for development purposes. Is there a reason why we should not build an executable binary?

[sourabhxyz]

cabal run is designed for development purposes. Is there a reason why we should not build an executable binary?

You are free to use static binary, I simply meant that this would not solve the delay issue you are seeing.

Could you please add a log message when the initialization starts and finished? Otherwise it is not really possible to tell where the time goes.

Logging in itself rely on initialisation of provider.

I am also not sure if we should be "resolving dependencies" in production. I still think that we should build a binary and distribute this.

Normally one would use cabal install ... to get the static binary, but it does out-of-tree builds which would break compile time git revision fetch. But one can get the built binary, in build directory (after the execution of cabal build all). For my machine, it is, dist-newstyle/build/aarch64-osx/ghc-9.2.8/geniusyield-server-lib-0.5.0/x/geniusyield-server/build/geniusyield-server.

[4TT1L4]

You are free to use static binary, I simply meant that this would not solve the delay issue you are seeing.

Thank you for the notice.

Logging in itself rely on initialisation of provider.

Could you please add this? So we could see different events, like: application started, initializing, initialization is finished. If no log messages are logged, then it is not really possible to tell where the time goes.

cabal build all

Thank you for pointing me to the binary and sharing the command. I can try to do the same and locate the binary in the docker container.

I was trying to install it, but install was failing with some error message.

[sourabhxyz]

Could you please add this? So we could see different events, like: application started, initializing, initialization is finished. If no log messages are logged, then it is not really possible to tell where the time goes.

Elaborating on my earlier message, to log we require to initialise a provider which takes ~30 seconds. So we cannot make a log before we initialise it.

[4TT1L4]

@sourabhxyz Please make sure that cabal install actually works for the server binary.