91–98 of 98 posts
This URL is blocked by my company's network because of a certain substring in the URL lol
Well if it isn't my arch-nemesis – my legally designated name. Maybe I should've gone for something with just my first name like drewsexpertblog.dev
printf '{HEX STRING}' | xxd -r -p | xxd
> printf '0a00000029416e746967756120616e64204261726275646107414709415447093032381d49534f20333136362d323a414713416d657269636173414c6174696e20416d657269636120616e64207468652043617269626265616e1543617269626265616e093031390934313909303239' | xxd -r -p | xxd
00000000: 0a00 0000 2941 6e74 6967 7561 2061 6e64 ....)Antigua and
00000010: 2042 6172 6275 6461 0741 4709 4154 4709 Barbuda.AG.ATG.
00000020: 3032 381d 4953 4f20 3331 3636 2d32 3a41 028.ISO 3166-2:A
00000030: 4713 416d 6572 6963 6173 414c 6174 696e G.AmericasALatin
00000040: 2041 6d65 7269 6361 2061 6e64 2074 6865 America and the
00000050: 2043 6172 6962 6265 616e 1543 6172 6962 Caribbean.Carib
00000060: 6265 616e 0930 3139 0934 3139 0930 3239 bean.019.419.029Earlier quoted context omitted.
I don't know where you're getting 300 MB/s from.
Page 5 of https://www-staging.commandprompt.com/uploads/images/Command... says "This system can checksum data at about 300 MB/s per core." It lacks page numbers. Page 5 is first page with gray box at the top of the page.
Earlier (page 4):
> How much CPU time does it take to checksum...
> ...a specific amount of data? This is easy to estimate because PostgreSQL uses the crc32 algorithm which is very simple, and (GNU) Linux has a command line program that does the same thing: cksum.
Yeah, using cksum as an estimate here appears to be very flawed.
Earlier quoted context omitted.
Page 5 of https://www-staging.commandprompt.com/uploads/images/Command... says "This system can checksum data at about 300 MB/s per core." It lacks page numbers. Page 5 is first page with gray box at the top of the page.
That's measuring 'cksum', which must have an awfully slow implementation. The document notes that this is distinct from measuring PG's checksum performance. (I think it's a pretty useless measurement.) Earlier (page 4): > How much CPU time does it take to checksum... > ...a specific amount of data? This is easy to estimate because PostgreSQL uses the crc32 algorithm which is very simple, and (GNU) Linux has a command…
https://github.com/komrad36/CRC has a massive section about it in the README. Really interesting.
Earlier quoted context omitted.
That's measuring 'cksum', which must have an awfully slow implementation. The document notes that this is distinct from measuring PG's checksum performance. (I think it's a pretty useless measurement.) Earlier (page 4): > How much CPU time does it take to checksum... > ...a specific amount of data? This is easy to estimate because PostgreSQL uses the crc32 algorithm which is very simple, and (GNU) Linux has a command…
That is weird. Seems like crc optimization is quite a rabbit hole. https://github.com/komrad36/CRC has a massive section about it in the README. Really interesting.
Earlier quoted context omitted.
Ahhh.. wouldn't that be better by using a percentage of filler words/total words in title threshold?? I don't know if a feature simply strips out the filler words in title, it's not always useful and rather harmful is what I would argue.
Humans work better. HN is small scale enough that a moderator can come along, collapse the off topic comments and fix the title, and it's not an issue.
Earlier quoted context omitted.
Humans work better. HN is small scale enough that a moderator can come along, collapse the off topic comments and fix the title, and it's not an issue.
Seems like title cleanup is a good use for an LLM actually. (Not to remove the human option, but as the first smarter pass instead of simple stopword lists.)
An LLM burns through how much power, compared to the tiny Arc server? You could outsource it, of course... But then you have a third party dependency.
Then you have the problem that LLMs continually and constantly change words to be "simpler" and destroy the very sensitive meanings, especially words in tech. Like auto-correcting Fediverse into Universe. Or C into C++.