Maoni Stephens

@maoni0

loves working on GC and other perf stuff; avid zoo-goer; wannabe hiphop dancer.

Vrijeme pridruživanja: travanj 2019.

Tweetovi

Blokirali ste korisnika/cu @maoni0

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @maoni0

  1. 23. sij

    after watching many hours of videos on Youtube with the playback speed adjusted, it's hard to prevent myself from innately wanting to adjust the audio speed when I hear someone talking too slow or too fast, only to realize the next second that I can't 😅

    Poništi
  2. 22. sij

    also /InMemoryCircularBuffer hasn't been working (it was an experimental feature to begin with) - there's an issue on it so I would suggest to not use it till that gets fixed (some day)

    Prikaži ovu nit
    Poništi
  3. 22. sij

    also, don't capture so many events if you don't need them. do pay attention to the Heisenberg effect. the events that can artificially lengthen the GC pause time by a lot are the GCHeapSurvivalAndMovement events (such as GCBulkMovedObjectRanges).

    Prikaži ovu nit
    Poništi
  4. 22. sij

    when PerfView pops up a dialog box that tells you there are a lot of lost events it's definitely being serious so please increase the buffer size arg (/BufferSize) to be larger, as it suggests.

    Prikaži ovu nit
    Poništi
  5. 21. sij

    an interesting project from MSR named Verona just got open sourced. inspired by languages like Rust. it has a concept of regions (not to be confused with what regions generally means in GC) to encapsulate object lifetime. explained in

    Poništi
  6. 25. pro 2019.

    for xmas dinner I made a salad and my SO made a brisket dish. I make a pretty mean salad (so that I can actually eat it myself) but it paled in comparison with the brisket. the only way it could compete is if I took the brisket, put it in the salad bowl and called it a salad.

    Poništi
  7. 25. pro 2019.

    I didn't use to have a favorite Christmas movie but now I do, it's called . on . made by a spanish studio: . so creative and so beautifully done. bravo!

    Poništi
  8. 19. pro 2019.

    one of the things I'm aiming to achieve in 2020 is to experience waldeinsamkeit more often. it's important. I recommend it to everyone.

    Poništi
  9. 19. pro 2019.
    Poništi
  10. 17. pro 2019.
    Tweet je nedostupan.
    Poništi
  11. proslijedio/la je Tweet
    17. pro 2019.

    We've open sourced our new GC Perf Infrastructure! It’s now part of the performance repo. has a really good write up about it. Check it out:

    Poništi
  12. 16. pro 2019.

    "so it was you who checked in the memory leak that caused us the 80 million cred outage, right before you left for you xmas vacation!"

    Poništi
  13. 16. pro 2019.

    the parking garage at work is more full than I had expected. why aren't people taking vacation yet😅

    Poništi
  14. 14. pro 2019.

    this will capture the SetGCHandle event with its stack, looks like this: your method call + !https://t.co/YrmwmNqGWe_STUB_PInvoke(...) + more stack frames + EventData GCHandleKind WeakLong + Event Microsoft-Windows-DotNETRuntime/GC/SetGCHandle

    Prikaži ovu nit
    Poništi
  15. 14. pro 2019.

    to verify (if you are hitting the issue and how much), you can use this perfview commandline to capture a trace: perfview /nogui /KernelEvents=Process+Thread /ClrEvents:GC+Stack+GCHandle /BufferSize:3000 /CircularMB:3000 collect

    Prikaži ovu nit
    Poništi
  16. 14. pro 2019.

    if you pass a delegate to a p/invoke call, you'd be hitting this GC handle leak issue that we just fixed in master and will backport to 3.1: . it's leaking long weak handles.

    Prikaži ovu nit
    Poništi
  17. proslijedio/la je Tweet

    GC Perf Infrastructure is now part of the performance repo. writes about it here:

    A white background with a purple speedometer showing a high rate of speed.
    Poništi
  18. 12. pro 2019.

    I rarely post stuff unrelated to tech but this is important - I wanted to urge everyone who hasn't donated to wikipedia to please do (unless you don't use it).

    Poništi
  19. 11. pro 2019.

    I think the confusion came from hearing the "no need to set the ref to null" advice which is applicable to variables on the stack (which are not managed objects!) managed by the jit. jit can figure out when you don't need that stack var anymore so it'll simply not report it

    Prikaži ovu nit
    Poništi
  20. 11. pro 2019.

    reminder - if you have a.f = b where a and b are managed objects, when you don't want a.f to refer to b anymore you do need to do a.f = null (or a.f = some_other_object) - unlike cats, GC is not psychic🤣

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·