Hi all, I was trying to decide if I should use full disk encryption on my new computer (i7-7700k, 16GB, Samsung 960 PRO - 1TB PCIe NVMe - M.2 SSD). I know there is overhead, and most of what I found online were for older SSDs. So thought I'd post my pre-bitlocker and post-bitlocker benchmarks. (I love how fast this disk is!)

AS SSD Benchmark:

No encryption

Seq read/write: 2355 MB/s, 1769 MB/s

4k read/write: 44.61 MB/s, 200.17 MB/s

4K-64Thrd read/write: 1694 MB/s, 1292 MB/s

Acc. time read/write: 0.042 ms 0.019 ms

Score read/wrote/total: 1975, 1670, 4624

With encryption:

Seq read/write: 2172 MB/s, 923 MB/s

4k read/write: 41.32 MB/s, 190.40 MB/s

4K-64Thrd read/write: 1487 MB/s, 227.82 MB/s

Acc. time read/write: 0.083 ms 0.019 ms

Score read/wrote/total: 1745, 511, 3086

Not too bad of an overhead. It seems write speed gets hit more than read speed, which I'm not sure why.

Are the claims in the following video true regarding Overhead Press (also known as military and shoulder press) and Pendlay rows.

Overhead Press Video Section

Row Video Section

That is, does the Overhead Press increase your chance of getting shoulder impingement syndrome if done repeatedly over a number of years, and does Pendlay rows (and bent over rows) increase the risk of developing herniated disks if done repeatedly over a number of years? Assume both exercises are done with good form.

On-chain solutions

Block size increase

The bigger the block, the more transactions it can carry. Block size was recently increased by 8KB to 72KB (a 12.5% increase); further increases will be applied over time based on ongoing system monitoring and overall network health.

Pipelining

Improves block propagation times by coalescing validation and propagation. The goal is for blocks to be propagated to at least 95% of peers within five seconds by reducing the ‘dead time’ between blocks (the block propagation overhead). This provides the headroom to make more aggressive scaling changes, such as increasing block size/increasing Plutus parameter limits.

Input Endorsers

Input endorsers improve block propagation times and throughput by allowing transactions to be separated into pre-constructed blocks. This improves the consistency of block propagation times and allows higher transaction rates.

Memory /CPU parameters for Plutus

Memory usage is more efficient across the chain. Specifically, there are memory improvements in Unspent Transaction Output (UTXO) handling, stake distribution, live stake distribution and pools, and hash representation.

Plutus script enhancements

Even more effective usage of the powerful EUTXO model through smart contract optimization, including:

• Reference inputs (CIP-0031) – Plutus scripts can inspect transaction inputs without needing to spend them. This means that it is not necessary to create UTXOs simply to inspect the information held by an input.
• Plutus Datums (CIP-0032) – Datums can be attached directly to outputs instead of datum hashes. This simplifies how datums are used, as a user can see the actual datum rather than having to supply the datum that matches the given hash.
• Script sharing (CIP-0033) – Plutus script references can be associated with transaction outputs, meaning that they can be recorded on-chain for subsequent reuse. It will not be necessary to supply a copy of the script with each transaction, hugely reducing friction for developers. Reusing scripts in multiple transactions significantly reduces transaction sizes, improving throughput and reducing script execution costs.

Node enhancements

Improvements will help even distribution of stake and reward computations across the epochs, thus providing greater headroom for block size increases. Also, memory usage is now more efficient. Memory compaction reduces RSS footprint, and memory sh

[first] [prev] [next]

Never forget that before your op is someone else's op, that while you're doing your run someone else is making their run, and after your run there is another beginning or doing their run. - Street Solo advice, Fighting Man's Magazine, Resource War Era, TerraSol.

Speaks blew the android's head off with his SMG, grabbing the body and yanking it out even as he leveled the SMG at the creation engine's computer system and pulled the trigger. The SMG had a whistling noise and Speaks knew the barrel was almost shot out.

The light SMG, firing 2.2mm rounds, was supposed to only see a few bursts worth the work, maybe one or two mags.

Speaks had burned through almost a dozen mags and the memory-plas was badly worn.

The android crashed to the ground and Speaks patted him down. He was carrying a heavy battle rifle, high caliber, loaded with heavy mass reactive gyrojet rounds, with an underslung 20mm variable munition grenade launcher. Speaks stripped grenades off the android's harness, checking them over and tucking them into his own gear.

A quick glance outside the conex showed that nobody was close and he scurried across and down a narrow gap between conex stacks. Lights stabbed down, searching through the conex containers and the equipment of the shipping yard. Speaks looked up and saw hovercraft in the air, some marked with LawSec and others marked with news stations.

"No, you idiots," Speaks swore, running for the fence.

That instinct raised up again and Speaks threw himself to the side, rolling, and a loud KARAK! sounded out right before a crater was blown out of the ferrocrete right where he would have been.

Speaks dropped a grenade as he rolled, coming up on his three feet and running for the conexes. The sniper was on the upper level highway access.

The sniper round blew through his shield and came so close that the air displacement ripped the end of his left antenna off. Speaks staggered, slapping his camo and putting on a burst of speed.

In the sky two of the LawSec HRT and one of the news hovercraft exploded. The unarmored news hovercraft fell to the ground, a burning hulk erupting in flames, the two HRT craft falling from the sk

I see a lot of folks on this sub running containers or even some kind of k8s clusters like minikube...

I run quite a bit of services but I haven't had an issue running them all on BM - Debian to be specific. I feel like it's more performant, customizable, and easier to troubleshoot when something isn't working.

What reasons do you run containers over Bare Metal?

Please be patient with me as I am just starting with zfs. So in the last week I was reading about zfs and I am considering switching my storage environment to it.

I have 2 x 1TB, 1x 2 TB and 1x 500 GB that I want to store my files one. I was thinking to have a big pool with them so that I can get close to 4TB. A RAIDZ from what I read is out of the question, yes? But a plain pool is feasible? I plan to buy another 4 TB for backup (plain rsync).

I also want to use encryption and I am thinking to use FreeBSD. My main machine is now OpenBSD and I will mount over the network the storage area.

Did I get something wrong. I gladly accept also reading suggestions

Thank you and a Happy New Year!

Later edit: After reading all the advices I came to the conclusion that it will be better to just buy another 1TB disk and have a Raidz that will offer me 2TB of space and I can use the 2TB disk as a backup.

I could not find a filesystem or filesystem overlay that I was happy with for storing plots. They all had overhead or downsides I didn’t find acceptable. All I wanted was a filesystem that could survive disk failures losing only the plots on that disk (not the entire pool), but still combine any remaining space at the end of each disk for more plots.

So I made one. I decided to release the code because this is probably a common desire. If you like to live dangerously, it is available at https://github.com/szatmary/PlotFS

Use at your own risk!

I don't want to step on anybody's toes here, but the amount of non-dad jokes here in this subreddit really annoys me. First of all, dad jokes CAN be NSFW, it clearly says so in the sub rules. Secondly, it doesn't automatically make it a dad joke if it's from a conversation between you and your child. Most importantly, the jokes that your CHILDREN tell YOU are not dad jokes. The point of a dad joke is that it's so cheesy only a dad who's trying to be funny would make such a joke. That's it. They are stupid plays on words, lame puns and so on. There has to be a clever pun or wordplay for it to be considered a dad joke.

Again, to all the fellow dads, I apologise if I'm sounding too harsh. But I just needed to get it off my chest.

Hi,

I'm new to Minio and the whole "object storage" thing, so I have many questions.

First:

If I understand correctly, Minio has standalone and distributed modes. Minio runs in distributed mode when a node has 4 or more disks or multiple nodes. If you have 1 disk, you are in standalone mode. In standalone mode, you have some features disabled, such as versioning, object locking, quota, etc.

I cannot understand why disk and node count matters in these features. If the answer is "data security" then consider the option if you are running Minio on top of a RAID/btrfs/zfs, it's not a viable option to create 4 "disks" on the same physical array just to access these features.

Second:

Lifecycle management: If you are running in standalone mode you cannot enable lifecycle management on the web interface, it's greyed out, but from the Minio client you can execute mc ilm add local/test --expiry-days 1 and objects will be deleted after 1 day.

Based on that experience, I think these limitations on the standalone mode are mostly artificial.

Can someone explain to me these things?

Let's just say earth was flat.. this is what would happen.

*Gravity Fails

First of all, a pancaked planet might not have any gravity People who believe in a flat Earth assume that gravity would pull straight down, but there’s no evidence to suggest it would work that way. What we know about gravity suggests it would pull toward the center of the disk. That means it would only pull straight down at one point on the center of the disk. As you got increasingly far from the center, gravity would tug more and more horizontally. This would have some strange impacts, like sucking all the water toward the center of the world, and making trees and plants grow diagonally, since they develop in the opposite direction of gravity’s pull.

The planet would simply collapse back into a sphere.

To shape a cosmic body into a disk (rather than a sphere), you've got to spin it very fast, says David Stevenson, a planetary scientist at Caltech in Pasadena, California. This would, unfortunately, destroy the planet by tearing it into tiny particles. In the 1850s, astronomer James Clerk Maxwell showed mathematically that a solid, disk-like shape isn't a stable configuration in the cosmos, in work he conducted regarding Saturn's rings. Maxwell's research predicted that Saturn's rings would be made of lots of small, unconnected particles; he turned out to be right. His math also explains why there are no planet-size disks floating around the galaxy. To flatten Earth without spinning it very rapidly, you'd need magic, or perhaps a galactic panini press. At any rate, a stamped-flat Earth wouldn't last for long. Within a few hours, the force of gravity would press the planet back into a spheroid. Gravity pulls equally from all sides, which explains why planets are spheres (or nearly so – depending on the speed of a planet's rotation, those forces may work against gravity to create a bit of a bulge at the equator). A stable, solid disk-like Earth just isn’t possible under the actual conditions of gravity, as Maxwell’s math showed.

And once you get rid of gravity, everything about our planet rapidly stops making sense

The atmosphere? Gone, because it's held to the planet by gravity. Tides? Gone. They're caused by the gravitational pull of the moon, which tugs on the oceans and causes them to subtly bulge out as it swings by.

The moon itself? Also gone, since every explanation of the moon's existence involves gravity. In the most widely accepted scenario, the moon was created when

Read Chapter 1 Here

Previous Chapter Here

Jolly Holiday to everyone!

****

The drone banked smoothly, staying just under the cloud cover. It had been deployed from the purple zone in Albuquerque, its simple brain knowing that it had one job. Lock on to the coordinates of the omnipad belonging to Jessica White and follow.

From Stace's little living room, Jel'si Chel'xa was directing the operation. While keeping Jessica alive was the top priority, there was a fantastic opportunity here. As Jel'si and Stace watched, the size of the organization that Jessica's father seemed to have contact with started to come into focus.

While the little blue sports car was stopped at a red light, a pickup truck swung out in front of it in an attempt to box Jessica in. She saw it coming and, before the truck could get in position, that little car was shooting through the intersection. From the drone's view they couldn't hear the tires squeal, but twin lines of smoke followed the vehicle's departure. Jel'si called it in, and soon the omnipads of the people in the pickup were identified and another drone was following them.

"They're tracking her." Stace was watching the feed intently, not dividing his attention like Jel'si had to. "They shouldn't even have known she has Daniel's car." As he watched, Jessica whipped around a corner in a controlled slide. An SUV that had been trying to run her off the road tried to follow her line and tipped over, rolling twice before coming to a stop on its side.

"Good," Jel'si said absently. "Every time someone tries to stop her it's another lead to shut down whatever's going on out there."

"Not good. She could be killed." The rebuke in Stace's voice drew Jel'si's attention.

"I'm sorry. You're right. But as long as she keeps driving like she has been, I don't think they'll be able to catch her." Jel'si kicked herself the moment she said it. The Goddess always had a way of punishing hubris.

An older muscle car, puffs of exhaust smoke trailing it, pulled out behind Jessica and started gaining ground. They were slowed by the early evening traffic, the tiny blue car weaving through comfortably while the larger Detroit steel had to force its way through tighter openings. Of course, they didn't actually have to CATCH Jessica. A passenger leaned out the window with a rifle

Do your worst!

I am trying to figure out what will be the fastest filesystem to use for development while ensuring that data are encrypted. I did some benchmarks and it turned that on laptop with i7-1165G7 CPU and Samsung 980 PRO SSD under Fedora 35 the overhead of LUKS or filesystem-level encryption can reach up to 39% depending on the file system and operation.

As I work with huge tree (Chromium-based browser), the most important operation for me is git status and compiling which can produces in short time a lot of small files. For benchmarking purposes I simulated the latter via find work -type f \( -name "*.c" -o -name "*.cc" -o -name "*.cpp" \) -print0 | xargs -P4 -n 100 -0 lz4 -k -m -f that compresses in parallel all C++ files on the system.

Without the encryption the results were (all filesystem were created with default settings on a primary partition, before each command all caches were dropped and sync was running after the each command, the CPU turbo boost were disabled, the result are the median of 3 runs):

git status on a clean tree (36 GB in total disk usage), sorted fastest->slowest

compressing C++ files

So without the encryption f2fs was a winner.

Now lets consider encryption (LUKS or filesystem-level encryption). For LUKS ther results are for aes-xts-plain64 (default) cipher with key size reduced to 256 bits from the default 512 to squeeze extra performance. Again, to reduce the noise in the results the CPU turbo boost was disabled.

git status on a clean tree (the third column - encryption slowdown)

compressing C++ files

Here the split is between BTRFS and F2FS. What is noticeable is how badly write operations under F2FS and XFS are affected by LUKS. Cloudflare blog mentioned how they improved LUKS performance. The options that they contributed are available Fedora 35, but in my case they made performance significantly worse s

They were cooked in Greece.

I'm surprised it hasn't decade.

Alot of great jokes get posted here! However just because you have a joke, doesn't mean it's a dad joke.

THIS IS NOT ABOUT NSFW, THIS IS ABOUT LONG JOKES, BLONDE JOKES, SEXUAL JOKES, KNOCK KNOCK JOKES, POLITICAL JOKES, ETC BEING POSTED IN A DAD JOKE SUB

Try telling these sexual jokes that get posted here, to your kid and see how your spouse likes it.. if that goes well, Try telling one of your friends kid about your sex life being like Coca cola, first it was normal, than light and now zero , and see if the parents are OK with you telling their kid the "dad joke"

I'm not even referencing the NSFW, I'm saying Dad jokes are corny, and sometimes painful, not sexual

So check out r/jokes for all types of jokes

r/unclejokes for dirty jokes

r/3amjokes for real weird and alot of OC

r/cleandadjokes If your really sick of seeing not dad jokes in r/dadjokes

Punchline !

Edit: this is not a post about NSFW , This is about jokes, knock knock jokes, blonde jokes, political jokes etc being posted in a dad joke sub

Edit 2: don't touch the thermostat

If you haven't watched it yet, this post contains mild spoilers. The short ticket is over but the long one goes until March, so plenty of time to catch up!

---

Akane plays hard and fast. Like, hard and fast, for real. We know that, right? Her tuning, therefore, is usually aimed at producing the shortest sustain possible with the greatest projection. For that, she tunes her drums quite high (for projection - higher pitched drums cut through amplified strings better), but with the beater head (top skin) turned slightly lower than the resonant head (bottom skin), which shortens the notes by reducing sustain (a tighter bottom head chokes the sound coming from the stick hitting the top). This allows her to play very fast whilst still sounding very clean, making each note perfectly discernible and balanced well with the others without any unwanted overlaps. She also uses gels (a semi-gelatinous sticky substance that comes in disks or hand-shapes for children to play with), but that’s more to reduce harmonic overtones - another trick to avoid unwanted envelope intersection, not so much to change the tuning.

So, anyway, forget all I just said, she threw all that out the window for the acoustic okyu-ji. Really clean slated it! First of all, she’s using rods, which are drumsticks made out of dowels bundled together with an adjustable rubber ring (which could be used for "tuning" them by opening them up to the drummer's desired sound). Because they are not one solid piece of wood, they produce a very characteristic sound, allowing them to become a percussion instrument on their own - if you play them on your leg, say, they would sound somewhere between a shaker and a clapper. Hers are Wincent W-19A.

Akane is playing them very open, with the ring about halfway back, giving it a lot of “clap” as it hits the drums and, especially, the cymbals (the harder surface makes the sound of the rods more pronounced). Mind you, rods aren’t necessarily quieter than normal sticks, it all depends on the drummer wielding them. Akane is playing very softly, taking full advantage of that rod sound, making it quite high in the mix (more about mic placement further down).

Back to tuning; her drums on this okyu-ji are tuned to a consonant note, meaning

Two muffins are in an oven, one muffin looks at the other and says "is it just me, or is it hot in here?"

Then the other muffin says "AHH, TALKING MUFFIN!!!"

Don't you know a good pun is its own reword?

For context I'm a Refuse Driver (Garbage man) & today I was on food waste. After I'd tipped I was checking the wagon for any defects when I spotted a lone pea balanced on the lifts.

I said "hey look, an escaPEA"

No one near me but it didn't half make me laugh for a good hour or so!

Edit: I can't believe how much this has blown up. Thank you everyone I've had a blast reading through the replies 😂

It really does, I swear!

Because she wanted to see the task manager.

[first] [prev] [next]

The air was climate controlled, fully filtered, and nearly canned. Not one molecule or atom was spared multiple filtration systems before it moved to the more secure levels deep beneath the earth. The air had a dry chill to it, one that seemed to seep through clothing and into the skin, setting into the muscle and fat beneath. The climate control kept the internal thermostat at 68F, supposedly comfortable to the occupants of the high security facility.

The man hated it.

He hated secure facilities like this. Constructed under the Atlas Missile Silo program, funded by FEMA's eternally black budgets, and so far off the books that no whisper of their existence reached those who were not cleared to know about them.

He viewed the nearly three hundred million dollars spent on it in the 1950's as an indulgence of a bygone era, despite the fact the facility was completed a little over a decade ago. Blasted out with dynamite, carved out by jackhammers, built by men he considered almost an alien species, the type of men who took such jobs and never spoke of them, merely cashed their paycheck and moved onto the next paycheck without regards to favors, possible hush money, or how it could benefit them beyond that meager paycheck.

The walls this far down were brushed metal, stencils here and there with strange acronyms that he didn't bother trying to understand.

He wasn't here to decipher strange glyphs on steel walls.

He was here to see the Queen of the facility.

A woman who's work was so closely guarded that her name was not redacted, it was never written down anywhere. She was referred to only as "Dark Queen", a nickname given to her by someone from within the labyrinth of government secret project administration.

On either side of him were his body guards. CIA agents of known reliability, who knew who granted favors and approved budgets. He had waived the military escort that had been offered when he had landed and the helicopter had been withdrawn into the facility.

He understood the soldiers as much as he understood the men who had carved out and assembled the facility.

The agents, those he understood.

The door he stopped at was heavy, inches thick, a heavy blast door that belon

But that’s comparing apples to oranges

And boy are my arms legs.

sloomy155's co-location homelab in 2021

Hello r/homelab

(super long post, maybe longest post ever here?)

Long time lurker, first time poster. In fact this is my first Reddit post ever(other than a couple of test posts to try to check the syntax). The only other social media I have an account on is Linkedin and that doesn't get used too much. My username doesn't mean anything it's just a random collection of letters and numbers.

I didn't even know the term homelab until I came across this subreddit probably a couple of years ago now? I have read a bunch of posts here, and have seen r/homelabsales and r/DataHoarder as well. It has been interesting to see other people's perspectives.

I never viewed my systems as a lab really, I have been hosting my own DNS/email/web/etc on the internet since about 1996. In my earliest days I volunteered at a super tiny ISP that one of my friends helped start and that was my first experience hosting live systems on the internet. That ISP closed down eventually and the remaining services ended up being hosted out of my home(though never was paid, I did it for the experience at the time). Here I am ~25 years later still messing around.

If you just want pictures, and don't care about my stories then here they are, I have comments on each image on imgur, small fraction of what I cover below:

• Homelab starting around 2001 (most geeky I suppose)
• First co-location server starting around 2006-2008 (Actual pictures taken much later, nothing special)
• Home lab starting around 2011 (nothing special)
• Homelab in 2021 (a bit better)
• Co-location in 2021 (coolest, to me anyway)

High level what I use my homelab for

• DNS, Email, Web hosting my personal stuff.
  • Some email/web/dns hosting for friends/family.
  • DNS: BIND (host my domains and have internal recursive DNS as well)
  • Email: Postfix + Cyrus IMAP + Spamasssin + Anomy Mail Sanitizer (config dates back to 2002ish)
  • Web: Apache
    • I could easily host all of the pictures I posted but used imgur since that is the more standard reddit thing to do.
  • DB: MySQL
• Owncloud (been using it since before Nextcloud existed just have stuck with it)
• Backing up my DVD/Bl

Heard they've been doing some shady business.

but then I remembered it was ground this morning.

Edit: Thank you guys for the awards, they're much nicer than the cardboard sleeve I've been using and reassures me that my jokes aren't stale

Edit 2: I have already been made aware that Men In Black 3 has told a version of this joke before. If the joke is not new to you, please enjoy any of the single origin puns in the comments

I will go first for Millia and Anji:

Millia:


1. j.H = In my opinion, her best move hands down. It covers the area below her and on both sides, making it a great crossup tool, especially when accompanied with airdashes.
2. H Disk = Her whole gameplan revolves around this move and rightfully so. It gives her the best mix in the game.
3. Haircar = This move is everything you might need. It's a combo tool, a mixup tool and gives a hard knockdown on hit.
4. c.S = A very unique c.S. It has two hits and both retain all options, some of which are Lows, Overheads and jump cancels.
5. Mirazh = The October patch made this move an important tool by giving it the ability to cancel itself into other special moves. It allows setups and combos that weren't possible before, as well as making older combos easier.
 Honorable mention: 6H = The main reason her corner combos exist and also has some uses in blockstrings and mixups.

Anji:


1. Fuujin and its followups = Anji's main mixup tool. The October patch made it possible to do the followups even before the Fuujin hits, making it a very tricky move to react to.
2. Kou = This move has several important purposes. It's a very scary anti air, an important combo tool, guard crushes if it happens to get blocked and gives a hard knockdown on hit.
3. Shitsu = The main oki tool. Used to lock the opponent down to ensure Anji can apply pressure safely.
4. 6H = A very unique command normal. Hits three times and all hits are special cancelable, making it a terrifying move when accompanied with Fuujin.
5. c.S = Nothing too crazy, just like all other c.S in the game. Main purpose in combos, meaties and blockstrings.
 Honorable mention: Spin = The move Anji is known for. It can backfire if used incorrectly, but a very good move that can make opponents think twice before doing anything.

And now I’m cannelloni

BamBOO!

They’re on standbi

On-chain solutions

Block size increase

The bigger the block, the more transactions it can carry. Block size was recently increased by 8KB to 72KB (a 12.5% increase); further increases will be applied over time based on ongoing system monitoring and overall network health.

Pipelining

Improves block propagation times by coalescing validation and propagation. The goal is for blocks to be propagated to at least 95% of peers within five seconds by reducing the ‘dead time’ between blocks (the block propagation overhead). This provides the headroom to make more aggressive scaling changes, such as increasing block size/increasing Plutus parameter limits.

Input Endorsers

Input endorsers improve block propagation times and throughput by allowing transactions to be separated into pre-constructed blocks. This improves the consistency of block propagation times and allows higher transaction rates.

Memory /CPU parameters for Plutus

Memory usage is more efficient across the chain. Specifically, there are memory improvements in Unspent Transaction Output (UTXO) handling, stake distribution, live stake distribution and pools, and hash representation.

Plutus script enhancements

Even more effective usage of the powerful EUTXO model through smart contract optimization, including:

• Reference inputs (CIP-0031) – Plutus scripts can inspect transaction inputs without needing to spend them. This means that it is not necessary to create UTXOs simply to inspect the information held by an input.
• Plutus Datums (CIP-0032) – Datums can be attached directly to outputs instead of datum hashes. This simplifies how datums are used, as a user can see the actual datum rather than having to supply the datum that matches the given hash.
• Script sharing (CIP-0033) – Plutus script references can be associated with transaction outputs, meaning that they can be recorded on-chain for subsequent reuse. It will not be necessary to supply a copy of the script with each transaction, hugely reducing friction for developers. Reusing scripts in multiple transactions significantly reduces transaction sizes, improving throughput and reducing script execution costs.

Node enhancements

Improvements will help even distribution of stake and reward computations across the epochs, thus providing greater headroom for block size increases. Also, memory usage is now more efficient. Memory compaction reduces RSS footprint, and memory sharing means we need less data instant

Let's just say earth was flat.. this is what would happen.

*Gravity Fails

First of all, a pancaked planet might not have any gravity People who believe in a flat Earth assume that gravity would pull straight down, but there’s no evidence to suggest it would work that way. What we know about gravity suggests it would pull toward the center of the disk. That means it would only pull straight down at one point on the center of the disk. As you got increasingly far from the center, gravity would tug more and more horizontally. This would have some strange impacts, like sucking all the water toward the center of the world, and making trees and plants grow diagonally, since they develop in the opposite direction of gravity’s pull.

The planet would simply collapse back into a sphere.

To shape a cosmic body into a disk (rather than a sphere), you've got to spin it very fast, says David Stevenson, a planetary scientist at Caltech in Pasadena, California. This would, unfortunately, destroy the planet by tearing it into tiny particles. In the 1850s, astronomer James Clerk Maxwell showed mathematically that a solid, disk-like shape isn't a stable configuration in the cosmos, in work he conducted regarding Saturn's rings. Maxwell's research predicted that Saturn's rings would be made of lots of small, unconnected particles; he turned out to be right. His math also explains why there are no planet-size disks floating around the galaxy. To flatten Earth without spinning it very rapidly, you'd need magic, or perhaps a galactic panini press. At any rate, a stamped-flat Earth wouldn't last for long. Within a few hours, the force of gravity would press the planet back into a spheroid. Gravity pulls equally from all sides, which explains why planets are spheres (or nearly so – depending on the speed of a planet's rotation, those forces may work against gravity to create a bit of a bulge at the equator). A stable, solid disk-like Earth just isn’t possible under the actual conditions of gravity, as Maxwell’s math showed.

And once you get rid of gravity, everything about our planet rapidly stops making sense

The atmosphere? Gone, because it's held to the planet by gravity. Tides? Gone. They're caused by the gravitational pull of the moon, which tugs on the oceans and causes them to subtly bulge out as it swings by.

The moon itself? Also gone, since every explanation of the moon's existence involves gravity. In the most widely accepted scenario, the moon was created when

I've been using BI for over 8 years now and am up to a dozen cameras at 1080p or higher resolution. I run this on a Lenovo i7 "tiny PC" (bought for $20 from a company surplus sale) and it's been working great. Idles at around 20% CPU most the time, however I recently upgraded 3 of my older cameras to newer and higher resolution cameras and system idle had climbed to 30-40% and would often jump to over 50, sometimes over 60% running both the server console and a web console on LAN.

So... I had never really understood the purpose of sub streams and had always just disabled them. However I did some searching to see what I could do to lower my CPU usage (and power usage since this is running 24/7). I stumbled upon a thread about BI CPU optimization and decided to give the sub streaming a try. Well, I'm blown away to say the least. I have been able to up the framerate to 15-20 fps on all my cameras and the resolution on a couple of them and am astounded to seem my CPU idle at around 9 to 12 percent! Higher frame rate, higher resolution, and a fraction of the CPU/power use. I now have enough overhead to feel confident in adding even more cameras if I want to without worrying about burning up my computer.

If you're not utilizing sub streams, I highly recommend you give it a try.

Side note: My only complaint right now is that the newer version 5.5+ has broken my timelapse camera clones that were working fine on 5.4- versions. It shows that there is video, but when I try to play it it tells me it's corrupted. This is using the alt timelapse record settings. I know lots of people do timelapse using jpeg outputs and recompiling, but that just seems like a giant hassle when BI already has a timelapse recording setting available. I hope they fix this because I'm back to just recording full 12hour clips and using the timelapse export function when I want to save something cool, but at the expense of disk space saving all that redundant video.