menaerus

53 ms·

931.
by menaerus 2y ago
They don't explicitly say that in the blog post but I assume that the engineering team behind this code does not run any workload performance experiments themselves but they only run the local (micro)benchmarks. Because of this I think
932.
by menaerus 2y ago
LSP doesn't always work without issues with large C and C++ codebases which is why one needs to fallback to grep techniques.
933.
by menaerus 2y ago
It is a claim unless there's a clear definition how is being calculated. And I don't see any besides the website saying "according to sources of our data"? Still, I don't understand how you could have double the mar
934.
by menaerus 2y ago
So how do you explain your claim being in so much contrast to the data that is easily checked and supplied by the @nabla9 comment?
935.
by menaerus 2y ago
Sort of but not really since EVs with their battery management are not far from being a smartphone.
936.
by menaerus 2y ago
You're right, there's more to it. For instance, Tesla S with 75 kWh battery pack has the autonomy of, optimistically saying, ~400 km and the battery pack alone weighs 530 kg (!). This range is I think already within a 90th percent
937.
by menaerus 2y ago
> As a contractor, you have B2B contracts which means you have to pay taxes over your revenue. In general this amounts to a tax rate in a range of 20%-30%. No shit Sherlock. You have to pay the taxes as a regular employee too. Go figure.
938.
by menaerus 2y ago
I think that Amdahl's law explains it much more succinctly.
939.
by menaerus 2y ago
130k amounts to 65 EUR/hr if you're working as a contractor. This is a low rate for an experienced and domain expert meaning that people with qualifications that think-cell is asking for already earn easily almost double than what
940.
by menaerus 2y ago
According to https://en.cppreference.com/w/cpp/ranges/filter_view return value of views::filter is either a new ranges::view or some sort of range adaptor that seems to be equivalent to a ranges::filter_view.
941.
by menaerus 2y ago
https://schedule.cppnow.org/wp-content/uploads/2024/02/Rappe... Slide nr. 21 (nr. 26 in PDF).
942.
by menaerus 2y ago
My, admittedly, not so big experience with std::ranges is that they generate an abnormal binary bloat in comparison to the traditional code, so, I also tried to argue against their usage in one my ex-teams who, paradoxically, wanted to achi
943.
by menaerus 2y ago
> In particular, C++ is fundamentally hostile to cross-language interopt C++ adheres to Itanium C++ ABI [1] which in turn adheres to SystemV ABI [2]. > to the degree that even C++ compilers struggle to maintain compatibility between t
944.
by menaerus 2y ago
Good question. I also may not understand that since as of today, and to my knowledge, top of the line Intel Xeon's can support up to 4TB per socket. This means that for a 8-socket system, largest amount of physical RAM would equate to
945.
by menaerus 2y ago
I don't think there's a need to explain to me how pointers work, or what to do to make this error/warning go away, since it should be pretty obvious from my response that this is something I know very well. I was only disputi
946.
by menaerus 2y ago
> gcc will compile this code and advance the pointer address by 1 byte. Yes, it's not standard conformant. https://godbolt.org/z/cjoYvjxGq <source>: In function 'void foo(int)': <so
947.
by menaerus 2y ago
The problem with musl is its malloc implementation. It is subpar when compared to glibc malloc. And we know that glibc malloc is generally subpar when compared to jemalloc. For large-scale applications with many (concurrent) (small) allocat
948.
by menaerus 2y ago
This can work only if you own the entire codebase and have all external dependencies that you depend on statically link (compiled) within your product. I also very much prefer this way of handling dependencies but it's not a solution f
949.
by menaerus 2y ago
Well no it isn't since malloc returns a void* and incrementing a void* is impossible for a compiler to figure out the offset that it needs to increment address for. For that operation to succeed/compile you need to cast the result
950.
by menaerus 2y ago
Besides that it makes some lock-free algorithms even feasible and some easier to implement, yes, it also can be used to downsize the memory pressure at the cost of extra CPU cycles if you know that the metadata you want to track fits in tho
951.
by menaerus 2y ago
Most of the ABI issues arise when you start to mix and match shared libaries produced by different compilers, or even the libraries produced by the different versions of the same compiler. Rust has none of that, nor does support dynamic lin
952.
by menaerus 2y ago
Yes, you're correct that generally you would not be able to use realloc for reasons you mentioned (and also because of destructors) but for simple POD (trivially-constructible) types I think it should be possible, no? In that case, rea
953.
by menaerus 2y ago
The important detail to make your theory plausible, and without a huge performance impact and/or jittering, is how the kernel memory management system is going to decide what exactly is those "relatively few pages" on a serve
954.
by menaerus 3y ago
My comment acknowledges the issue mentioned by the parent comment and extends it with extra information out of my own curiosity, and which others may find useful or valuable too. Or not. I don't care. There surely could exist std::vect
955.
by menaerus 3y ago
> instead of dereferencing lhs on the third line: emplace_back returns a reference to the inserted item, so it's a &unique_ptr...and that reference is invalidated by the rhs emplace_back reallocating the vector. Correct but only
956.
by menaerus 3y ago
They hire an engineering manager that has never or hardly has done any serious coding. Alternative is that they hire an engineering manager experienced in coding but strongly opinionated and highly biased. Middle ground is an endemic occurr
957.
by menaerus 3y ago
Yes, indeed, it is very ridiculous to pull out arguments such as "who are you". I mean, wtf? Your replies demonstrate lack of technical depth in certain areas and which makes me personally doubt in your experiment results. And you
958.
by menaerus 3y ago
> I'm guessing that this discussion would be more productive if you would please say who you are and the company you work for. I'm Brendan Gregg, I work for Intel, and I'm well known in the performance space. Who are you?
959.
by menaerus 3y ago
> What is interesting about this vulnerability is that it is a logic bug in the memory management unit of the Arm Mali GPU and it is capable of bypassing Memory Tagging Extension (MTE) The rest of the article appears to be describing tha
960.
by menaerus 3y ago
I don't think I have. I was only responding to the factually incorrect statement of yours that pgbench is a microbenchmark. > which was about whether databases could even have micro-benchmarks. No, this was an argument of yours that

More ›