24 Hours of Daytona 2021

[Kenadian]

Okay, I switched with you. Will be an early morning for me too, but not as early as for you

Thanks @Deb. I'm usually a complete mess this time of the morning particularly after little rest from Saturday morning onward.

 

[Skid_Marc_]

I put together a schedule for @Kelley G and @Anson Bennette, and now I NEED to make a coffee run..

 

[Kelley G]

what setup did we decide on? I’m fine with any of them.

 

[Brainling]

On the 6 driver schedule, you can switch Ken and I for the early stints if that's too early for @Kenadian

 

[Kelley G]

Maybe a stupid question. Are we still using teamspeak or are we on discord now? Its been a while lol. Reason I'm asking is TS isn't connecting for me.

 

[Brainling]

Maybe a stupid question. Are we still using teamspeak or are we on discord now? Its been a while lol. Reason I'm asking is TS isn't connecting for me.

Address has changed. In your bookmark, in the Server Address or Alias box just put B2O. No .com or anything, just the alias B2O.

 

[ShadniX]

Oh boy, this was a long one. Thanks for racing everyone, it was an awesome time as always.

@Kenadian (and for anyone else who wants it): Here is a download link to the full replay file for our split: https://www.cosmocanyon.de/b2o/2021-01-24_Daytona24_-_Split35.zip
It is a 21GB file. Please let me know if there are any issues with the download.

 

[Deb]

Yeah, long race, with several stressful incidents, but enjoyed driving with everyone again

 

[Brainling]

Was long, but I think from our team perspective, we drove a great race. Short one LMP2 having a complete brain meltdown, we had a top 10 car no problem and I think a top 5 was within reach.

 

[Jes_971]

Heres the post-mortem from the Daytona issues - https://members.iracing.com/jforum/posts/list/3791012.page

 

[Brainling]

I'm actually super impressed they found and fixed a deadlock that quickly. Deadlocks can be notoriously difficult to track down and fix.

For those curious, a deadlock is when two threads, or streams of work, in a piece of software attempt to acquire a lock to a resource (generally a network resource, a database table, chunk of memory, etc). but due to a bug they both sit in the "waiting to lock" state, while the lock is never released. The threads then "deadlock", effectively going to sleep forever waiting for a lock that never releases. They are a notoriously difficult class of bug to debug and fix and are one of the main "There be dragons here" issues in multi-threaded programming.