Skip to content

Instantly share code, notes, and snippets.

@CrazyPython
Created January 2, 2019 00:08
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save CrazyPython/fd82230b51153ab048e18893f0c8a2b6 to your computer and use it in GitHub Desktop.
Save CrazyPython/fd82230b51153ab048e18893f0c8a2b6 to your computer and use it in GitHub Desktop.

I want read-only access to your GitLab repository, with the permission to propose merge requests. Do that and I'll considering continuing staying on arras-dev.

If not, I'm gonna ask to join Fillygroove/Hellcat's server as a co-dev, and I'm gonna contribute my anti-lag efforts and my CTHD there.

I have three prongs of evidence that strongly lead me to believe that GC is the issue. And although I can't disprove the null hypothesis like you want me to, intuition trumps proof when you want speed.

Testing

We can do the Meausirng / Testing after you try out my fix in prod. But until then, it's not worth it for me to try to replicate your freeze-every-15-seconds behavior and do a controlled trial just to prove what my intuition already knows. Because I can't replicate your freeze-every-15-seconds behavior on my server by just adding lots of bots, and to do so I'd probably have to set up a VM (Or register for and wait for an OpenShift account.) with extremely limited memory size and allocate some swap to replicate it, or use some weird new V8 options I just learned to simulate the same conditions that might not even replicate the same environment your Arras servers are experiencing. Not happening-pretty difficult and seriously time consuming, I could be making CTHD for fillygroove in the same time. The best thing we can do is send you a fix and have you try it on your Openshift account.

You're probably willing to try the fix it were easy to try. Well, giving me read

RBT distrusts everyone. But you're not RBT. Trust me. Trust fillygroove. I am not your equal, but if you trust me I can at least better serve you.

By making it slow and difficult to merge code into arras.io, you splinter the arras development community, leading to the creation fo private servers. I asked fillygrooove why she didn't participate much in arras-dev. She said that, among other things, she doesn't want to wait a month to get her changes merged.

After reading that, I discovered my own anger at the slowneess to merge changes. Why was it so difficult to get my changes merged? Why was it so difficult to test whether my changes worked? #2 isn't your fault. I storngly beleive my fix only didn't work because of s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment