@quixoticjeremy said in Random Thread - Anything Goes:

@dafyre said in Random Thread - Anything Goes:

@minion-queen said in Random Thread - Anything Goes:

Wow look at what I have missed in the last few minutes. You people shouldn't be left alone

Especially not on a Friday.

Exactly. Most of us are going to take any excuse we can get to not actually do work.

The Hoff says, "get back to work, you".

@quixoticjeremy said in Random Thread - Anything Goes:

Oh jeez, I feel like he's staring into my soul.

Starring into your soul, you say?

@minion-queen said in Random Thread - Anything Goes:

Wow look at what I have missed in the last few minutes. You people shouldn't be left alone

Yes, look at what you have missed!

@minion-queen said in Random Thread - Anything Goes:

Wow look at what I have missed in the last few minutes. You people shouldn't be left alone

You have been missing the Hoff!

@quixoticjeremy said in Random Thread - Anything Goes:

@quixoticjustin said in Random Thread - Anything Goes:

@quixoticjeremy said in Random Thread - Anything Goes:

@quixoticjustin said in Random Thread - Anything Goes:

For everyone's sake, don't google that show, it is not a real thing yet.

Not a real thing .... "yet".... ummmmm I don't think it ever will be tbh.

Don't be doubting on the Hoff!

I don't doubt him! I doubt that a musical named Cock Beach will every be made lmao

Challenge accepted.

@quixoticjeremy said in Random Thread - Anything Goes:

@quixoticjustin said in Random Thread - Anything Goes:

For everyone's sake, don't google that show, it is not a real thing yet.

Not a real thing .... "yet".... ummmmm I don't think it ever will be tbh.

Don't be doubting on the Hoff!

Playa de Gallo

For everyone's sake, don't google that show, it is not a real thing yet.

And there will be an associated drinking game to go with it.

I do believe that "Cock Beach: The Musical" was just proposed.

@quixoticjeremy said in Random Thread - Anything Goes:

@rojoloco said in Random Thread - Anything Goes:

@scottalanmiller said in Random Thread - Anything Goes:

@rojoloco said in Random Thread - Anything Goes:

@danp coming this fall on NBC.... David Hasselhoff in..... COCK BEACH!!!!!!

that would actually be a popular show.

I'd watch it. The Hoff is still the bomb. Plus the female co-lead would be smokin'.

As long as he doesn't sing. He once did a bunch of musicals, and every time he was doing a duet it really turned into a trio, him, his counter part, and his friggen vibrato which was so obnoxious that I couldn't handle it. Then again maybe I just can't handle the hoff.

As long as he doesn't? I think singing will be a requirement!

It is Friday and that means a day of Sodium releases! Lots on the schedule for today, so getting a place ready to keep everyone up to date on what we are pushing.

One thing coming later today (we hope) that I am looking forward to is the inclusion of avatars. Time to make things look a little more polished.

Do reboots have to happen at the time of update? Or can they wait? Any reason to delay updates rather than just delaying the reboot?

@quixoticjeremy said in What Are You Doing Right Now:

@quixoticjustin said in What Are You Doing Right Now:

@nerdydad said in What Are You Doing Right Now:

@quixoticjeremy said in What Are You Doing Right Now:

@quixoticjustin said in What Are You Doing Right Now:

It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.

Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.

Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.

Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.

Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.

Beat you to it

I saw that

@nerdydad said in What Are You Doing Right Now:

@quixoticjeremy said in What Are You Doing Right Now:

@quixoticjustin said in What Are You Doing Right Now:

It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.

Yep. Already doing my best to make sure everyone knows I will be unreachable all night tonight.

Have y'all considered going to just one release a week, such as every Friday night or Sunday night or so? Might be easier for bug tracking.

Bigger releases mean more breaking bugs all at once with less time to catch and address them. Mitigating bug issues is a key reason for more releases. That way bugs come out faster, get fixed faster and releases are way smaller. So we are troubleshooting tiny bits of code changes instead of big groups of changes, to find where bugs exist.

Think about it like a system that is broken. If you just patched one library, or just patched hundreds and the system and something breaks, it's really easy to find the problem when you only updated one thing. But if you updated your whole system and something breaks, the problem could be anywhere and you are far more likely to be trying to find multiple issues at once that might even interact with each other.

It is Friday, so that means loads of Sodium news and releases today. Getting set up for that this afternoon. We do about half of our weekly releases on Fridays, so lots to keep us busy.

@matteo-nunziati said in Using In-Memory Databases, Anyone?:

@quixoticjustin you mean volatile session data?

Yes, data that is needed for performance and consistent session behavior but if lost would not have a real impact.

Some, more or less, standard things about in memory databases...

1. They require enough memory to load the entire database at "load time." There is no "making do with less memory." It just won't load. It's like a ramdisk for databases, there is no going to disk when you run out of memory, it just dies on you.
2. They take longer to fire up because they need to get everything from disk to ram before they can do anything.
3. While they might persist to disk at some point, that's not necessarily part of the database design. That's optional by product.
4. Data integrity is normally handled by clustering rather than writing to disk. You rely on high availability and serve requests from multiple nodes.

@quixoticjeremy said in Using In-Memory Databases, Anyone?:

@quixoticjustin said in Using In-Memory Databases, Anyone?:

Caching a traditional database to memory and having an in memory database do not behave the same. A pure in memory database has advantages to structure that databases writing to disk do not. There is no need to structure the data in preparation for writing to disk.

Was wondering when you'd show up on this one.

Finally one I can talk about.

With Sodium, for example, we use a "traditional" on disk database for the main data (well all data right now.) But we know that as we scale that that will not suffice for performance. Moving to in memory databases for things like session data is a standard model for application acceleration. Redis rules in this particular space, as it is a key value pair in memory cluster aware database system.

Redis is not Sodium's guaranteed in memory option, but certainly on the short list.