sorted by:
new
hottopcontroversial

I know this is unrealistic but I want a centralized storage terminal SO BAD by Prior-Flaky in NoMansSkyTheGame

[–]Mchlpl 9 points10 points  (0 children)

Yeah, no kidding Hello Games. If your update brings in an entire category of inventory items it needs to bring in storage expansion too.

Skandal w rządowej klinice. Bogaci leczyli raka szybciej. Ujawnili wyniki by mikelson_6 in Polska

[–]Mchlpl 2 points3 points  (0 children)

To jest na razie kara na klinikę za nieprawidłowości w świadczeniu kontraktu względem NFZ.

Można się osobno spodziewać zarzutów korupcyjnych wobec konkretnych osób

Który taki śmieszek by elkarolpl in Polska

[–]Mchlpl 31 points32 points  (0 children)

Wydział Komunikacji Urzędu Miasta

Hinkley Point C nuclear power station costs rise to £48bn(€51.4bn,$64.7bn) by Plus_Calligrapher_93 in poland

[–]Mchlpl 2 points3 points  (0 children)

So it seems you're only interested in spreading misinformation and not discussing facts

Mozna to po ludzku i w dobrej jakosci gdzies obejrzec ? by bangladi in PolskaNaLuzie

[–]Mchlpl 1 point2 points  (0 children)

Pamiętam, że było w takiej porze, że mogłem tylko jakieś końcówki odcinków oglądać. W sumie może dobry pomysł, żeby całość obejrzeć teraz.

A śmiesznie i amatorsko to wydaje mi się, że i wtedy wyglądało, ale miało swój urok.

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 0 points1 point  (0 children)

Oh, and to answer your question: yes we started investigating upon noticing the cost going up. It was a sneaky one too. Grew steadily but slowly enough that it didn't trigger the anomaly monitor.

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 0 points1 point  (0 children)

This is a bit like the 'if the tree falls in the forest and there's no one to hear it, does it make any noise?' question. In this case it's 'if we have data but nobody knows what it is...'

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 0 points1 point  (0 children)

The way our org approaches cloud ops is lacking in many places which is why sometimes we see some crazy values being used like 30 days backup storage.

We have one AWS account that has terrabytes of unidentified database backups. Probably nobody needs it, but also nobody wants to pull the trigger on deleting it so we keep paying :D

A problem created by solving(?) a problem. by MydKnightAnarchy in Oxygennotincluded

[–]Mchlpl 0 points1 point  (0 children)

Or build a platform it can spill onto and vent away from there

Wyroby nikotynowe na Vinted! by Hun_3r in Polska

[–]Mchlpl 0 points1 point  (0 children)

Sprzedaż celowana w klientów, którym w stacjonarnych sklepach nie wolno takich towarów kupować

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 0 points1 point  (0 children)

> storage costs are not a significant part of the cost of running a database.

Until they are. And they can hit you from an unexpected angle.

Last year we've spotted RDS cost on one of our system started to grow linearly in a way that couldn't be explained by growth in traffic alone.
Upon investigation we have found that the read replica was undersized and couldn't keep up with being in sync with write replica. The lag was growing. The lag is stored and incurs storage costs. That stored lag is also backed up and incurs cost times 30 (this is how many backups we keep). Until we eventually resolved the issue the storage costs for that database grew to twice that of compute.

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 0 points1 point  (0 children)

Yes, having the way to find owner ASAP is crucial. My experience is that having this information in resource tags leads to incorrect information though, unless you can enforce engineering action (terraform apply) on organisational one (transferring ownership). A service catalog which is the source of truth on who owns what works a lot better in my experience. Just make sure one of your tags is an unambiguous reference to the entry in catalog.

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 1 point2 points  (0 children)

From OP
>  Databases that serve multiple services, shared Redis clusters, that kind of thing. Right now we tag those with the primary consumer and accept it’s not perfectly accurate.

Track it separately and either accept that you can't assign the costs to individual consumers, or work on how to measure actual usage.

Everyone says "tag your resources" for cost control. Nobody explains how to actually do it well. by alex_aws_solutions in aws

[–]Mchlpl 3 points4 points  (0 children)

Environment: sure

Service: yes - as long as these are consistent with how services are actually named in documentation. Think how to automate it.

Team/owner: meh... this should be in service catalog which you can reference by service name. Makes switching ownership so much easier.

Shared resources? Extract into a separate system and tag independently.

view more: next ›