The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I was spending £40 ~ £50 pa on embossed rolls (and getting a lot of failures with the Chinese ones) but for about £15 I get 1000 bags (150x200) and £30 for 1000 200x300 which should last a while ... they do biodegradable ones as well but they aren't suitable for freezers unfortunately.
The chamber vac cost about £300 (cheap Chinese industrial jobbie) but it has the advantage of packing liquids as well as solids. And that was handy when Rich next door was about to drive to Snowden with two big pots full of cawl using just tin foil as a lid ... I figured he'd have to stop outside Brecon and open the tailgate to let the stew out ...
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
It's less important for meat actually, that you can do basically as good, without sous vide, if you know what you're doing. Which most people don't though.
The big deal is with vegetables IMHO. They're getting cooked in their own juices, at the right temperature, which gives a lot more intense flavours and the perfect consistency.
But it's not for everyone, and I'm only doing it on weekends, because time. And I like balsamic dressing as well
So I ended up refactoring and adapting an old microsoft codeplex project for doing an in memory B+ tree, because it was already tested and was released under MPL which is nearly the same license as MIT.
And it's all exposed using a happy dictionary interface.
However, I'm looking to do an ISAM file backed B+ tree.
Well, the problem with that is the records have to be fixed length.
It's a limitation the in memory BPlusTree doesn't share (but honestly should, not for consistency, but for performance although with the GC it doesn't really matter)
fixed length means fixed length strings or *some* mechanism for embedding blob style pointers to fields. (Which also makes them non-searchable through the primary query mechanism - you have to use secondary queries and you can't have these as part of your keys). People familiar with RDBMS systems know these restrictions well.
Also, the trouble with that is I don't know quite how to store those fields.
Currently, the file would be laid out in blocks of fixed lengths. If I start storing blob fields in it, then i lose the fixed block layout and perf that comes with it.
I was thinking of laying out the file in fixed length blocks but having the blobs span multiple blocks. That means a bit of wasted space, but not a huge deal.
It does complicate things though because then i need an additional linked list in the file to find the blob fields quickly by reference - possibly another index.
This is the house that jack built. It has turned into a castle.
Rube Goldberg smirks in my general direction.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.