3 ms·

"high-performance" We might have differing opinions about that. (I've got experience for example in Windows kernel mode drivers and service development.)

throeaaysn 3y ago
[dead]
- vardump 3y ago
  No guesstimates, but it's generally very bad. Especially when there's some corporate "security" software in the loop. And that's the case you have to really code against.
  - dataflow 3y ago
    You already realize it's your security software that's slowing your system calls. Blaming it on the registry makes no sense. It's like blaming HN for being slow because your ISP is slow.
    - vardump 3y ago
      Not mine, but the actual customers'. "Works for me" is not going too far. Besides, registry is not a rocket even on a clean system.
dataflow 3y ago
What are you comparing against here that's leading you to a different opinion? Are you claiming file I/O would be faster or that you could write the equivalent functionality faster? Also note that performance isn't just speed either.
- vardump 3y ago
  For example SQLite is superior. That said, on Windows you kinda have to use registry, especially on the kernel driver level.
  - dataflow 3y ago
    > For example SQLite is superior. First... where are you getting this from? I just spent half an hour writing a an incredibly simple benchmark and all I see is SQLite being something like 20x slower than a registry query, seemingly caused by repeated locking & I/O system calls. This is on a trivial database with just 1 table with just 1 row, vs. a registry that's on a machine that's been running for years. If you have a benchmark that can disable the locking and get comparable performance, I'd love to see it. Not that it would mean anything though, given the next point. Second, even if it were somehow faster... you'd be comparing apples to oranges. The registry has a bunch of things SQLite isn't designed for: security integration with the rest of the OS, a hierarchical structure, OS hooks for monitoring & interception, multithreaded access, etc. Have you tried doing these with SQLite before praising how fast it is? > That said, on Windows you kinda have to use registry, especially on the kernel driver level. Is it common for drivers to use SQLite to store configuration information in any OS? I dare say I've never seen this.
    - vardump 3y ago
      "Is it common for drivers to use SQLite to store configuration information in any OS? I dare say I've never seen this." It's not. You're going to use your assigned registry hive for it.

throeaaysn 3y ago

[dead]

vardump 3y ago
No guesstimates, but it's generally very bad. Especially when there's some corporate "security" software in the loop. And that's the case you have to really code against.
- dataflow 3y ago
  You already realize it's your security software that's slowing your system calls. Blaming it on the registry makes no sense. It's like blaming HN for being slow because your ISP is slow.
  - vardump 3y ago
    Not mine, but the actual customers'. "Works for me" is not going too far. Besides, registry is not a rocket even on a clean system.

dataflow 3y ago

What are you comparing against here that's leading you to a different opinion? Are you claiming file I/O would be faster or that you could write the equivalent functionality faster? Also note that performance isn't just speed either.

vardump 3y ago
For example SQLite is superior. That said, on Windows you kinda have to use registry, especially on the kernel driver level.
- dataflow 3y ago
  > For example SQLite is superior. First... where are you getting this from? I just spent half an hour writing a an incredibly simple benchmark and all I see is SQLite being something like 20x slower than a registry query, seemingly caused by repeated locking & I/O system calls. This is on a trivial database with just 1 table with just 1 row, vs. a registry that's on a machine that's been running for years. If you have a benchmark that can disable the locking and get comparable performance, I'd love to see it. Not that it would mean anything though, given the next point. Second, even if it were somehow faster... you'd be comparing apples to oranges. The registry has a bunch of things SQLite isn't designed for: security integration with the rest of the OS, a hierarchical structure, OS hooks for monitoring & interception, multithreaded access, etc. Have you tried doing these with SQLite before praising how fast it is? > That said, on Windows you kinda have to use registry, especially on the kernel driver level. Is it common for drivers to use SQLite to store configuration information in any OS? I dare say I've never seen this.
  - vardump 3y ago
    "Is it common for drivers to use SQLite to store configuration information in any OS? I dare say I've never seen this." It's not. You're going to use your assigned registry hive for it.