Round 23 Announcement

[NateBrady23]

We're back from the holidays and ready for a Round 23 plan!

Are there any must have fixes / upgrades before we start doing preview runs?

Please tag @msmith-techempower as he'll be leading the Round 23 effort and link any issues you see as blockers. We'll discuss what we can tackle and then lay out some dates.

Thanks and Happy New Year everyone!

[msmith-techempower]

We are continuing to merge pull requests, and anticipate the current run and the next one to wrap late next week (the week of Jan 13). To that end, the official Round run will likely begin on or around Jan 20, which means that pull requests will not make it in after ~Jan 17 (give or take).

[Dreamsorcerer]

I'd like #9348 included, but not sure what has changed with the DB setup in the past years. There's been a number of optimisations in recent releases (although I'm not sure how much they'll show in simple benchmarks, likely more noticeable in real-world scenarios), so would be great to get this included.

[joanhey]

Please update the message in https://tfb-status.techempower.com/

With the information about the final date for PRs

[msmith-techempower]

I've updated https://tfb-status.techempower.com/ to indicate the preview round has started.

[p8]

@msmith-techempower Is the current run the official run?
If so, should the message be updated to reflect this? 🙂

[msmith-techempower]

Yes, I have updated the announcement to make it clear that the official round run is underway.

[joanhey]

Sorry, you changed again !!
You can decide which round, but please never change it !!

The last round have more frameworks failing than the last round before with all the frameworks !!

PD: I see you have preview and run started, I can understand it !!

... W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble/InRelease Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out ...

PD: sorry, but it's so !!

[p8]

@joanhey These seem network issues, not related to new commits.
It would be nice if an official round retried all failed frameworks.

[msmith-techempower]

I'm missing something here - what is the problem and what do we believe the resolution is?

I'm not sold on "fails intermittently so we need a redo on [x, y, z]" without a really good reason.

[msmith-techempower]

Okay, that run just finished and we had some other issues in the office around electric (... MAYBE there was a short power-outage or similar and MAYBE that impacted the run???).

So, I'm going to say it was not the official round run, and we'll give this next one a chance.

TFB-Status has been updated accordingly.

[tif-calin]

So we're close to an official Round 23? It's basically becoming an annual event at this point. Every year I look forwards to:

• a new StackOverflow survey
• the next interop
• the latest TechEmpower Web Frameworks Benchmark

[franz1981]

I see that quarkus didn't run the full matrix of tests which usually it run indeed, so I hope it is not the full run.

[msmith-techempower]

See guys? This is why I let another run go. Quarkus appears to have run fine.

But in all seriousness, the diffs do show that there was [something amiss] during the previous run. I think this is the one.

Going to let you guys make some comments, arguments, etc., but also going to suggest that was the run, and start prepping the results and blog post.

Also, I'm not sure why I'm not getting notifs here - @ me if there's something important.

[CypherPotato]

No more PRs will be accepted after Jan 20?