Derek Janisch

@OfficialTwinkey @FACEIT_Darwin @FACEITcs At the very top level, Premium Match is by far the largest match type. Expanding the number of locations can give you more possible players to be matched with (i.e. 5-6.)

YO @FACEIT_Darwin everyone has been pushed down to this elo and YET we Q for 30-40 min GIVE US GAME

@iAxessor @SwillCS Can you share the match?

@SwillCS 2400 elo getting put in a game filled with level 8s like wtf

this faceit elo reset has the worst lobbies known to man

@VECTIZZ1 @FACEIT_Darwin @FACEIT @FACEITcs The best settings to expand the pool of players we can match you with are server locations. Every location you include adds more potential players we can match you with. If you guys can support it, I'd suggest expanding to 5-6 locations where you get a reasonable ping.

@FaceitDerek @FACEIT_Darwin @FACEIT @FACEITcs Thanks for your answers ! But tbh even with all the settings unchecked + tried to expand the research I was still waiting 30+ min with my trioQ, but when they got into duoQ they instantly got a match, should I avoid the TrioQ for now ??

Hello @FACEIT_Darwin @FACEIT @FACEITcs, I'm streaming, and as a streamer, we need to entertain our community, and we can't right now because we are waiting atleast 20-30+ min everytime we launch the Q. EVEN IN PREMIUM. Will it be fixed soon ? We pay Premium to wait over 20 min...

@f0rest Locked in 🔒

alright im back

@CaneTV__ Make sure you have the latest game configuration setup in the queue. I believe it's in the queue settings it'll say (5v5 Legacy) and select (5v5), and you will have the latest gamde mode with the new version Cache.

@FaceitDerek Hey in my hub we tried playing new cache and the loading screen was new cache but the map itself was the old version :( pls fix!

With it defaulted on, that means most matches should have Cache as an option to play on. Do you think Cache could overtake Mirage & Dust2 for the most played map by tomorrow?

@VECTIZZ1 @FACEIT_Darwin @FACEIT @FACEITcs Lastly, if you want to have more options of players to play with, you can pause your queue, expand your settings (i.e. add in more locations) and keep your spot in line when you requeue.

@VECTIZZ1 @FACEIT_Darwin @FACEIT @FACEITcs I would also suggest avoiding restarting your queue; it puts you back at the line. It's better to wait in the queue, rather than a hard restart.

The updated version of Cache is now live on FACEIT. Cache is now selected by default in map preferences and can be deselected without needing to subscribe or change your other map bans.

@Mercantio @FACEIT_Darwin The start of the season is both a reset and a placement. So you did climb through your placements, you broke through the reset, and start ahead of others who were of similiar Elo prior.

@FaceitDerek @faceit_darwin check ticket: #13209841 I went 8-2 and lost elo when I have an average of 1.11 rating. I had activity last season to maintain elo.

@tripexcsgod @guthrieecs @FACEIT_Darwin @FACEIT Our reset takes into account your past activity and also how consistent you are in your matches. Your matches before the reset were significantly worse in performance than the ones during your placements, so the system hit you a little harder than most.

very interesting, i was 3850 elo when season 7 finished. I won 7 out of 10 games to get my elo and i got 2863. Btw my friend streamer @guthrieecs was 3400 elo at then end of season 7 and won 6 out of 10 games and got 2997 elo. How is this system working @FACEIT_Darwin @FACEIT wtf

@Muri11_CZ @FACEIT_Darwin It's because it's a soft reset into placements. The higher you are in Elo, the more the reset affects you. So it is possible to earn Elo from the reset + placement, but it heavily depends on how much the reset was.

@FACEIT_Darwin How does the placements work? I thought if you perform good in the placements, you can get much better elo, but yours didnt change even tho you had 7W out of 10 or does it look at your faceit rating or is it just random just like premier rating?

Placement games went pretty well for me, 7W, 3L Two of those losses were on Inferno when I was basically comatose 😅 How did yours go? And how are you finding the experience so far? 👇

@skrillacs @bajmiz9n You should see the Elo back now.

@FaceitDerek @bajmiz9n 🐐

dojebana jest ta platforma ciesze sie ze istnieje

@skrillacs @bajmiz9n Hey skrilla, yeah, I can confirm those four games are in my list to be refunded.

@FaceitDerek @bajmiz9n @FaceitDerek please please, check my profile. Last 4/5 games of the night yesterday, trio q with avg 2650 elo, for 5 games in a row both our teammates were 2k elo flat. Unplayable games faceit.com/en/players/skr… Am i going to get this elo back?????

@HeMancsgo Congrats!

9-1 Placements 🗿

I wanted to take this opportunity to share some background information on what happened during the FACEIT outages over the last 2 days. My goal here is to provide more information about how the platform responded under record demand. I hope some of you find these insights interesting or can learn something from them for yourselves. I’m trying to bridge the gap between non-technical and technical folks, so some things might be too nuanced for some, while other things might be too high-level for others. On Wednesday, April 22, the amount of traffic to our website far exceeded even our highest forecast, especially so early in the day at 1PM CEST. Like most cloud native software companies, we have more servers provisioned than necessary, including auto-scaling mechanisms to handle traffic spikes. Yet, your enthusiasm for our platform outgrew even these generous buffers, making us push the upper safety auto-scaling threshold. As we recognized the increased traffic, our engineering team started to increase the ceiling of our auto-scaling configuration in terms of physical cloud limits and Kubernetes configuration, practically provisioning more web servers to handle the load. Unfortunately, we had already reached a critical point at which existing servers (Kubernetes Pods, for the techies here) were failing faster than new ones could spawn. What happened in this moment is that the extremely spikey traffic caused people to get errors, making them refresh continuously, which sent our servers into a death spiral that they couldn’t recover from without intervention. As we stabilized the website, the spike in players queuing up led to our Matchmaker falling behind, resulting in much longer than usual queue times. The surge of matches spawning furthermore led to our game server architecture not being able to scale quickly enough. Our game servers are run on so-called bare-metal servers, which are not virtual cloud servers but actual machines, guaranteeing the best performance and latency. Bare-metal machines take longer to provision and deploy into our fleet, and they also sometimes have supply issues. Last week, we put in orders that maxed out available capacity in some of our regions and are waiting on more deliveries. During this period, the fallback is cloud scaling to ensure players are not waiting 10 minutes for a server. However, this scaling mechanism was unable to keep up with the demand. Since Wednesday, we've had additional deliveries, increasing server numbers to an all time high. On Thursday, April 23, as a follow-up to Wednesday's surge, we greatly increased the horizontal scaling of our Matchmaker. However, as we hit peak hours, this extra load pushed our proportionately scaled matchmaking database to its limit. The Matchmaker is using a Redis database, which should be operated in an environment where 20% of memory capacity should be reserved for the system memory, so that it can perform crucial operations like cleaning up stale data while keeping the database performing normally. Given the increased amount of matchmaking capacity, we had to basically double the amount of memory allocated to said database. There was a change made to our configuration files about a year ago that tipped the ratio of Redis and system memory below the 20% threshold. This hidden bottleneck never caused an issue during normal operations, but under the extreme pressure of Season 8's launch and our newly expanded queues, the database stalled. Write requests began timing out, which caused a cascading failure across our game queues. We eventually managed to scale the database up further, while keeping already active matches from cancelling and the platform as a whole operational. The “issue” here is that a zero downtime scaling of such a system basically requires a new replica to spawn and replicate all data from the old instance before connections can be rerouted, which takes time and system resources. Once that scaling safely concluded, we fully restored the service. We are now auditing all of our database configurations to ensure similar resource imbalances are not hiding anywhere else, and reinforced the Matchmaking database with extra system memory headroom.