For the longest time I’ve been trying to track down the thing that is cause tons of GC in our app. I think I found it. http://cl.ly/JxxZ
@PatrickTulskie checked out OobGC? zero GC within the request cycle is possible ;)
-
-
@bascule We’re actually doing OobGC every 5 requests already. It used to be 70-100ms/req. Getting to 5-7ms is a big win lol -
@PatrickTulskie oof @ every 5 requests -
@bascule Would you do it more or less often? -
@PatrickTulskie we do it every 12 requests at@LivingSocial, and we see zero GC in the request cycle -
@bascule I might space it out a bit and see what happens. Background checks have enormous amounts of data so moving the needle is tough.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.