Felix Urbasik on Nostr: nprofile1q…kktgp This looks like you constantly allocate memory which then gets ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqwkaun0pqpnzswj2c0gtn2aggllvxwzvt855qnft7vw3zcc5dh2swkktgp (nprofile…ktgp) This looks like you constantly allocate memory which then gets cleaned up by a garbage collector in regular intervals.
Not alarming. There is probably way worse JS code out there. If you want peak performance, you could look into ways of avoiding allocations in JavaScript. But that's something you would have to research yourself, I'm afraid.
For starters, look out for code that handles large strings, and try avoiding creating copies of them.
Not alarming. There is probably way worse JS code out there. If you want peak performance, you could look into ways of avoiding allocations in JavaScript. But that's something you would have to research yourself, I'm afraid.
For starters, look out for code that handles large strings, and try avoiding creating copies of them.