Applied Energistics wierdness

[Lathanael]

Dude... did you read ANYTHING I posted? Apparently not.

I KNOW each card, whether 1k or 64k, has a limit of 63 UNIQUE items. That is not what this is about.

Let me make this REAL simple for you: One stack of Cobble (and only one stack of cobble) uses 16 bytes on a 1k, 40 bytes on a 4k, 136 bytes on a 16k card and 520 bytes on a 64k card. Got it?

Why does 'Item X' take up more space on a cell with more space available than one with less available. It's like saying a bucket of water is uses 1000mB in the bucket, but if you put it into a 10 million mB storage tank, it's now going to consume 100,000mB in that tank, but then when you go to use it, you will remove 100,000mB from the tank but will actually only get 1000mB. 8oz of water is still 8oz of water whether it's in a 10oz container or a 3,000oz container. a 1GB file is still 1GB whether it's on a 250GB drive or a 4TB drive. Got it?

I KNOW that different items use different amounts of space on a card.

I KNOW that if I want to store 40k cobble, I need a 16k Cell or higher (in theory).

I KNOW that if I want to store 300 UNIQUE items, I need FIVE ME storage cells, whether 1k in size or 64k in size.

The problem is this (Again, real simple): my 4k card was 58.9% full (2414 of 4096 bytes used). When I transferred its contents over to the 16k card, the 16k card was 51% full (8366 of 16384). I didn't ADD any items. I didn't CHANGE any items. I simply MOVED everything off a single 4k card onto a single 16k card and the 16k card was still over 50% full, just like the 4k card. The 16k card should have been something like 15% full, not 50%.

At any rate, I've posted this info in his thread on MC forum. We'll see what he says.

He has read all of your rant but it seems you have NOT read the link he has given you. Because everything is explained in there. The best explanation (as a real life example) is given here:

Ok, your real life life example is actually wrong. Larger drives have larger block sizes. There is a minimum amount of drive space even 1 byte will take up. The larger the drive, the larger this block size. This is why you see 2 numbers when you look at the property of a folder in windows. It will show you number of bytes, and then it shows you number of bytes on the drive. There is wasted space.

Example: http://i.imgur.com/qwVCHfB.jpg

StorageCells work like this too. On a 1k cell an item takes up 8 bytes per type, on a 64k cell it takes up 512 bytes per type. So if you fill a 64k cell with stacks of only one item and 63 different stacks 32264 bytes of your cell are already used (63*512+8) on a 1k cell it is 512 (63*8+8).
This is working as intended!

 

[Greevir]

OK so out of curiosity I gathered this data from a creative world ME system. Basically this means that for normal storage usage a bunch of 1k or 4k drives should be used. When you want to store a massive amount of one or two items, then use a 16k or 64k drive.

https://docs.google.com/spreadsheet/ccc?key=0Ahhb2G9ZH-bMdGQzTEJ0THlINHVoTXRKc0hEVzh3S0E&usp=sharing

Thats generally true, but also take into account that each individual cell uses power. So while having 64 1k cells may be better for storage, it sucks up far more power than a single 64k cell. It's something you have to balance out.

 

[Artheos]

I personally have settled on 4k storage disks. They seem to be the perfect balance for me and my needs.

 

[Bibble]

Really it's designed so that if you try a "spam this for best effect" system, you're going to end up losing out. I tried using ME chests in conjunction with logistics pipes, but they don't connect, you need a full system (grr), but that seems to be the easiest way of micro managing your cells.


Sent from my iPhone using Tapatalk - now Free

 

[Harvest88]

Really it's designed so that if you try a "spam this for best effect" system, you're going to end up losing out. I tried using ME chests in conjunction with logistics pipes, but they don't connect, you need a full system (grr), but that seems to be the easiest way of micro managing your cells.


Sent from my iPhone using Tapatalk - now Free

You know you only need the drives and disks and just take the things out of one ME interface. Put a provider, a Basic pipe for defualt routing and power draw and also a request pipe.

 

[Bibble]

You know you only need the drives and disks and just take the things out of one ME interface. Put a provider, a Basic pipe for defualt routing and power draw and also a request pipe.

Yeah, but I didn't want the full (controller, etc) system. I just wanted to use them as standard chests. Also AE/LP seems to have a throughput limit on the interfaces which starts hitting when you get too complex of a system.


Sent from my iPhone using Tapatalk - now Free

 

[Harvest88]

Yea I believe it's an item every 5 ticks or whatever the import/export buses are.