Optimize subscription

[vikiival]

Context

At this point we have it a very fancy behaviour of SubSquid API that it causes memory leak

Note

for humans - it means that app feels ultra slow

This is 99% caused by subscriptions and their incorrect usage

Task

1. identify subscriptions in our app
2. if possible optimize their size

• if not possible we can always update schema

3. if possible replace subscription with polling :)

Convos

Global

[vikiival]

Assigning @preschian as he probably was implementing subscriptions last time, also help from anyone from @kodadot/internal-dev is welcomed :)

[preschian]

Assigning @preschian as he probably was implementing subscriptions last time

Hah, me? I think it is false mention

one more reason for this: https://github.com/kodadot/ops-internal/discussions/1745

[vikiival]

Hah, me? I think it is false mention

noted

one more reason for this: https://github.com/kodadot/ops-internal/discussions/1745

Won't help :), you will get same issue on other drops, chains etc

• app is already slow

[preschian]

Won't help :), you will get same issue on other drops, chains etc

Why?

For example, this PR works fine: #10713. unless, I just found some drops doesn't have supply functions