Programming thread

  • 📧 If you are an employee of a T1 ISP, US datacenter, or related company please get in touch at josh@kiwifarms.net. I have some questions.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Ahriman said:
Guess I should start learning more about Protobuf.
Click to expand...
Attaboy.

Protobuf is the preferred means of serializing structured data to a binary format within SWI-Prolog. https://www.swi-prolog.org/pldoc/man?section=protobufs-main

Basically, it's supported everywhere, but it's quite remarkable that the SWI project chose Protobufs, as it is the only binary serialization format that it supports natively. Prolog being a weird high-level language, it's unusual to see Prologs caring much about binary serialization.
 
analrapist said:
Attaboy.

Protobuf is the preferred means of serializing structured data to a binary format within SWI-Prolog. https://www.swi-prolog.org/pldoc/man?section=protobufs-main

Basically, it's supported everywhere, but it's quite remarkable that the SWI project chose Protobufs, as it is the only binary serialization format that it supports natively. Prolog being a weird high-level language, it's unusual to see Prologs caring much about binary serialization.
Click to expand...
Yea but judging by those graphs, it only pays off when you're handling well over 50k requests/second. Arguably one should still prefer gRPC since you'd be future-proofing your API, but still. On the low end, REST takes the lead.
 
canalCrab said:
>mmap

Pfff, look at that casual. sbrk is where its at.
Click to expand...
Perhaps, but mmap also allows me to reserve address ranges without allocation, as well as map files in and out of memory to disk
I really like it
 
You must log in or register to reply here.
Back
Top Bottom