Hacker Newsnew | past | comments | ask | show | jobs | submit | wardb's commentslogin

I always recommend Airalo to collegues. I travel a reasonable amount and Airalo has been reliable for me and available in a lot of countries. Last year they didn't have Singapore (I think this was re-added?) and it was annoying and expensive to buy an eSim at the airport. Reminded me how great their service is.


Grafana Labs employee here => On the linked articles: I'm not aware of any caching being used in the writing data to S3 part of the pipeline other then some time based/volume based buffering at the ingester microservices before writing the chunks of data to object storage.

The linked Loki caching docs/articles are for optimising the read access patterns of S3/object storage, not for writes.


Yes. Thanks for the reply!


lol. clearly a ChatGPT answer


+1 Loki is designed for object storage as backend. Persisting all data (so not storage tiering) on object storage vs local storage gives you cost savings, increased durability and simplified operational at scale.


Unfortunately it's severely misunderstood in the benchmark how Grafana Loki should be queried for high cardinality data. See also https://github.com/SigNoz/logs-benchmark/issues/1


Thanks for creating the issue. Yeah, this is what we also found, that Loki is not designed for querying high cardinality data.

But since Loki is many times used in observability use cases, where there is sometimes a need to query high cardinality data, we thought to include it.


That's incorrect, Loki is designed for querying high cardinality data.

The difference is that in Loki the index is only used for metadata around the source of the log lines (environment, team, cluster, host, pod etc) for selecting the right log stream to search in.

Parsing, aggregation and/or filtering of log lines on high cardinality data is all done at query time using LogQL. See also https://www.youtube.com/watch?v=UiiZ463lcVA and this live example where a 95th quantile is calculated using the request_time field of nginx logs https://play.grafana.org/d/T512JVH7z/loki-nginx-service-mesh...


This is kind of the issue with an interested party/vendor running benchmarks like these. Be it by pure dumb luck or malfeasance you are much more likely to configure and be knowledgeable about your own product than the others and toss out responses and results that are wildly inaccurate/misleading.


SAP Concur is a complete nightmare for managing expenses. It's so bad that it will ruin your entire weekend, leaving you feeling frustrated and drained. The interface is a convoluted mess that is practically impossible to navigate, and entering expenses takes forever.

The expense categorization system is an abomination that will drive you insane with its constant mistakes and errors. The approval process is a black hole that sucks up your expenses and never spits them back out. I feel SAP Concur is the worst software ever created for expense management, and using it makes me wish I never had to do expenses again.

Expensify is so much better. The OCR isn't great though


I'm with OVH because of their NA presence (Canada). Prefer dedicated servers because of the bang for the buck. Hopefully that's in Hetzner's roadmap too


How is OVH these days? It's been years since I used them heavily, back when I was doing some game server stuff, and they were the standard in the community I was in.


I often had speed issues between OVH servers in the US and Hetzner servers in Europe. But not sure which fault it was, never got anywhere. Hetzner support was helpful, they claimed it was on the side of OVH. OVH never really got back to me on this.


besides the short network outage a few weeks ago it has been rock solid for me in the CA datacenter


They also had small issue in Strasbourg earlier this year.


small issue = whole datacenter burned down


The not-indexing the log lines in Loki doesn't mean you can run complex queries on Loki. I've made a video to explain this concept: https://youtu.be/UiiZ463lcVA


Out of Order support is available in Loki's main branch and included in the next release. It's already live in production on Grafana Cloud. https://grafana.com/blog/2021/09/16/avoid-dropped-logs-due-t...

High availability in Loki is supported in distributed mode. Helm chart here: https://github.com/grafana/helm-charts/tree/main/charts/loki...


Yes, I'll try the next release, that's why I said it wasn't released yet :)

Regarding HA, I meant something beyond a k8s deployment.


This description is too funny :) It does have a high amount of old man screaming at the cloud. You can have a lot of valid critical views of cryptocurrency (environmental impact / gambling aspect ), but this his view is very unhelpful

Does CPB actually has anything to say here? I was expecting "De Nederlandse Bank" to be the organisation to set the rules here.


This is purely the personal opinion of a pubic official. Neither organization has any regulatory power on this topic. CPB is an independent agency providing economic prognoses and analysis. DNB is in charge of monetary policy but doesn't have the power to completely ban cryptocurrency.

Anyway, when the ministry of finance investigated a crypto ban back in 2018 they concluded that it would be completely impractical to enforce such a ban. I don't think that has changed in any way.


Does CPB actually has anything to say here?

No. They deliver forecasts and analysis for government policy. https://en.wikipedia.org/wiki/Bureau_for_Economic_Policy_Ana...


> but this his view is very unhelpful

Did you read it? If so, why do you take this opinion?

> Does CPB actually has anything to say here?

The CPB does analysis to inform public policy making, they're not a legislative body. Neither is the DNB for that matter, the Ministry of Finance would make these laws.


No, it's not a regulator and thus has no actual say over this matter. It supports policymakers by evaluating the economic effects of their plans.

https://www.cpb.nl/en/what-does-cpb-do


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: