Deepcase worked slower and crashing after 24 hours

suenot commented 1 year ago

Describe the bug

I think that problem in new architecture, because all connection go through deepcase. Need to revert to old architecture and pass all connections directy to deeplinks. New architecture has been chosen for supporting codespaces, but @Menzorg said, that there was another solution to support codespaces.

Problems:

Deepcase worked slower. Client handler became slower.
After 24 hours deepcase crashed.
Harder to debug proxing ws connetions.
Respond time became larger

Expected Behavior

No response

Current Behavior

No response

Steps to reproduce

No response

Environment

No response

suenot commented 1 year ago

https://github.com/deep-foundation/deepcase-app/issues/223 connected problem, by my opition

Konard commented 1 year ago

We may find a way to make this configuration optional.

You can also use connector to connect Deep.Case directly to Deep.Links

Please measure the difference in performance, so we will have precise data to make a decision.

deep-foundation / deepcase