storage object

previouslyembarrassed-deactivat  asked:

I'm confused about how an Se-Ni/Ni-Se user's memory works (as opposed to an Si-Ne/Ne-Si user's). I hear a lot about Si with "I read it in a book" or remembering the same sketchy looking guy from earlier that day. Are they just more apt to forget things?

Every type has a memory storage system, and can be forgetful. The difference lies in Extroverted Sensing and Introverted Sensing.

Extroverted Sensing is outside itself, noticing the details of what is happening, so memories stored through Se are “just the facts.” The colorful sequence of events involved, devoid of emotion. Se works with Ni, which is a subjective interpretation of these events, seen through the person’s desire for deep inner meaning. You may still get a bias when someone references memories stored in Se, but reciting these memories is platonic: this happened, and that resulted, and this is what it means.

Introverted Sensing is inside itself, viewing what is happening through an internal, subjective perspective directly tied to sensations, including emotional ones. Memory is influenced by how the person sees and feels about what it is observing. It colors the memory based on how the person felt about it. These are not the cold, distant facts of what happened but a personalized depiction of events. And when that person revisits that memory, the emotions of when it first happened return with it. That’s why Si-users have such trouble overcoming trauma; because they cannot step back and objectively view their memories the way a Se-user can. Each time the memory returns to their mind, they experience the same emotions (fear, anger, rejection, embarrassment, etc) that they had the first time around. Si is paired with Ne, which allows them to see the broader implications of this event, and how it ties into their life story (or someone else’s). Ne strives for connections to other events.

Both parties have an objective memory storage system (Se/Ne), but only Se is truly aware of what actually happened, because Ne immediately starts breaking events down into symbolic meaning. It starts seeing things as connected, and expanding, and in terms of “all-encompassing” (this event happened to me; as it happens to us all), while Se gauges events, then starts searching for deep internalized meaning in them.

For example, when my ENFJ friend talks about her childhood, it is a stating of the facts of what happened with an implication of what it means for the whole of her human existence. When I, a Si-user, talk about my past, memories return to me about particular things that made an impact on me, either positively or negatively; and I feel those same emotions coming back to me as I talk about them. My whole body warms up and a feeling of intense happiness accompanies memories of fun times, friends, the excitement of discovering something new, etc. Bad memories have a physical reaction in me too; I start to hyperventilate, shake, or feel intense guilt, dread, or depression.

Si does place more emphasis on book learning than Ni. Si tends to trust things that have been around for a long time, which means book information is likely to be trusted; so they use it as a reference point (both for fiction and non; it doesn’t matter). Ni more often trusts its own perception of things.

Korean Folk Magic (Spirits): Eopshin

Eopshin (업신) is one of the many household deities (가신) found within Korean homes. Eopshin can be male or female, but is typically regarded as female. Even though the other household gods are present in inanimate objects like storage jars, Eopshin is unique in that she is often represented as a snake, weasel or toad but can also be represented by Jujeori (주저리) which are huge pointed bundles of pine needles.

This deity’s “domain” tends to be the storage parts of the home, like the pantry or shed. She oversees the household material possessions and brings in wealth and protects the home. The rumor is that if you see a snake in any part of your house that is not the roof, it’s a bad omen and a sign that the home is in decline (this could refer to the physical home or the material wealth of the family). To get the snake back up to the roof, koreans would burn human hair, hoping the smell would drive the snake to return to the roof. 

There is another version of this deity called Ineop (인업) who typically has a human form that looks like the clone of the person Ineop “attaches” itself to. After Ineop attaches to a person, she will grant them prosperity and protect their home.

This was spurred on by Eopshin visiting me last night. I was in an attic area (pretty much as close to the roof as I’m ever going to get) and she descended onto me, wrapping around my neck slowly. I was worried I was going to accidentally squish her because she blended into my hair and myself so well, but I got a strong sense of “Don’t worry about that”. At my feet were two ferrets (mustelidae, just like weasels) and at first I assumed it was my deceased ferrets visiting me again (they do that sometimes). But the one closest to me was pure white in color and had black eyes so I knew these weren’t my pets. I walked around the room carefully. Eopshin didn’t say much, just had the aura of “I’m here, I will protect you”.

A list of Gem abilities

Most of the gemsonas I see around seem to not have any non-standard Gem abilities except for the occasional elemental power. But Gems in the show have a wide variety of different powers, and even a single Gem can have a shit-ton of different abilities. So, I’m making a list of Gem powers that have been seen in the show so far.

Feel free to look at this for inspiration if you’re stuck on figuring out your OC’s abilities. No credit is required.

Keep reading

Basic Power Storage Spell

Everyone needs objects or thoughts that help us staying strong.
This easy spell will allow us to store energy and positive thoughts inside an object, just like a battery.
You can charge your desired amount of items, however, excess is not recommended as the objects might drain more power than you can handle.

Elements neccessary for this spell:
• One of our favourite objects. It can be anything but preferably small in size.
• As an extra*: you can combine other spells/rituals that you know will improve the effects.

The steps are the following:
1. Hold your object with your left hand.
2. Kiss it.
3. Bring it close to your heart and count up to ten following your heart’s beat.
4. You must sleep that night near it so it can charge up.
5. Done. Everytime you feel the need of energy, just touch it.

You might want to recharge it eventually, as its power ends in a period of time or uses; estimate it around a week.
It’s not recommended to perfom this spell if you are having a bad day or you’re not feeling okay in general as the object may absorb your negative energy.
However, if that’s the desired effect you’re seeking you can do it, energy will be stored although a different kind of it.

anonymous asked:

on every scale from molecular analysis to large scale storage hard cookies objectively outperform soft cookies, its not a matter of taste here!

It absolutely is a matter of taste, we’re talking about cookies. Studies show that 99% of people prefer soft cookies and that the 1% is just weird.

Why do we hold our breath when we lift heavy objects?

It’s to brace/strengthen your core. Your body is “smart” enough to realize you’re about to put a lot of strain on your lower spine, so it forces you to contract all the muscles in the area to bolster it. This is why a belt helps deadlifts or squats, it gives something for those muscles to push against, further protecting the spine.



Weekend Hashtag Project: #WHPretro

Weekend Hashtag Project is a series featuring designated themes and hashtags chosen by Instagram’s Community Team. For a chance to be featured on the Instagram blog, follow @instagram and look for a post announcing the weekend’s project every Friday.

The goal this weekend is to capture creative photos inspired by the style, fashion and design of the recent past. Some tips to get you started:

  • Thrift stores can be great places to start gathering inspiration. A few fun pieces of second-hand clothing can quickly set the tone for a photo shoot with a little imagination.
  • Don’t be afraid to think big. Seek out vintage cars, funky furniture and even retro architecture.
  • Finally, some of the best finds from the past might not be further than family storage. Seek out the objects that loved ones once cherished and share photos with their stories.

PROJECT RULES: Please add the #WHPretro hashtag only to photos taken over this weekend and only submit your own photographs to the project. Any tagged image taken over the weekend is eligible to be featured Monday morning.

Yahoo Cloud Object Store - Object Storage at Exabyte Scale

Yahoo stores more than 250 Billion objects and half an exabyte of perpetually durable user content such as photos, videos, email, and blog posts. Object storage at Yahoo is growing at 20-25% annually. The growth is primarily driven by mobile, images, video, and user growth. Yahoo is betting on software defined storage to scale storage cost effectively along with the durability and latency guarantees.

Object Storage Landscape at Yahoo

What is “object storage”? Images and photos in Flickr, Videos, and documents, spreadsheets, and presentations exchanged as Mail attachments are classic examples of “objects.” The typical quality of this class of data is “write-once-read-many.” Traditionally, Yahoo has used storage appliances for object storage. As Yahoo is increasingly becoming the guide for digital information to our users, object storage need in Yahoo is growing rapidly. Additionally, application characteristics differ in access patterns, durability and latency needs, and cost targets. To support growth cost effectively and meet the varying application needs, object storage in Yahoo requires different tradeoffs. We need the flexibility offered by software defined storage to deliver these tradeoffs.

Why Software Defined Storage?

Key benefits of software defined storage are:

  • Cost-performance tradeoff: Allow applications to choose performance and cost tradeoffs with different hardware and durability configurations using the same software stack.
  • Flexible interfaces: Ability to choose industry standard API, embed client libraries in applications, or even use proprietary API where required. Industry standard APIs allow seamless migration of applications from public to Yahoo private cloud.
  • Different storage abstractions: Leverage the same storage software stack across Object, Block, and File abstractions, thus reducing  R&D and operational costs.

Cloud Object Store (COS) is Yahoo’s commodity hardware based software defined storage solution. In partnership with Flickr we have completed a multi-petabyte initial deployment of COS. And, in 2015, we plan to offer COS as a multi-tenant hosted service, and grow COS by ten-fold to support Flickr, Yahoo Mail and Tumblr. That is 100s of petabytes of storage to be supported on COS.

Under the Hood

COS is deployed using Ceph storage technology. We evaluated open-source solutions such as Swift and Ceph, as well as commercial solutions.  We chose Ceph because it enables consolidation of storage tiers for Object, Block, and File with inherent architectural support. Also, being an open-source product, Ceph provides the flexibility needed to customize for Yahoo needs.

Deployment Architecture

COS deployment consists of modular Ceph clusters with each Ceph cluster treated as a pod. Multiple such Ceph clusters deployed simultaneously form a COS “supercluster” as shown in Fig 1. Objects are uniformly distributed across all the clusters in a supercluster. We use a proprietary hashing mechanism to distribute objects. The hashing algorithm is implemented in a client library embedded in the applications.

After several trial runs and software tweaks, current deployment of each Ceph cluster is approximately 3 petabytes of raw capacity to provide predictable latency both during normal operations and recovery from hardware failures. Since each cluster consists of tens of commodity servers and hundreds of disks, it is highly likely that components will fail frequently. High disk and network activity occurs during recovery due to rebalancing of objects, which in turn increases object read latency during this phase. Capping the size of each cluster allows us to limit the resource usage during recovery phases in order to adhere to latency SLAs.

Yahoo users expect their images, videos and mail attachments to be perpetually stored, and made available instantaneously from anywhere around the world. This requires high data “durability” guarantees. Durability is typically achieved in storage systems either via redundancy or encoding. Redundancy can be provided through extra copies of data or replicas. On the other hand, encoding can be provided via traditional mechanisms like simple parity, or more sophisticated mechanisms like erasure coding. Erasure coding breaks down an object into fragments and stores them across multiple disks with a few redundant pieces to tolerate multiple failures.

The usable capacity of each cluster depends on the durability technique used. We currently employ erasure coding with each object broken down into eight data and three coding fragments. This mechanism, called 8/3 erasure coding, can tolerate up to three simultaneous server and/or disk failures with about 30% storage overhead for durability. This is much lower than the 200% overhead in case of replication.   

The two durability techniques offer different price points and latency characteristics. Replication offers lower latency but a higher cost, whereas erasure coding reduces cost (sometimes by up to 50%)  at a slightly higher latency. We can also deploy different storage media such as SSD, HDD and Shingled Magnetic Recording (SMR) drives to enable different service levels depending on the application.

Technically, it is possible to scale a COS supercluster by adding storage needs to increase the capacity of the component clusters. However, this will lead to rebalancing of data within the component clusters, thereby creating prolonged disk and network activity and impact latency SLA. To scale COS, our preferred approach is to add COS superclusters as needed similar to adding storage farms. This approach is consistent with our current appliance-based storage solution that applications are already familiar with.

Latency Optimizations

COS is in the serving path for many Yahoo applications and has to guarantee latency SLAs to ensure consistent high quality of user experience. We have implemented over 40 optimizations in Ceph to realize 50% improvement on average, and 70% improvement in 99.99% latency. Fig 2 depicts the latency chart before and after the optimizations under normal operations. The latencies in this chart are measured across objects of different sizes in the Flickr workload.

Some of the major optimizations are:

  • Redundant parallel reads with erasure coding: Currently, we have deployed 8/3 erasure coding scheme for durability. Increasing the parallel reads to 11 chunks, instead of the default 8 employed in Ceph, and reconstructing the object upon first 8 retrievals provided significant improvement in long tail read latency. This reduced average latency by approximately 40%.
  • Recovery Throttling: Upon disk and node failures, Ceph automatically initiates recovery to maintain high durability of objects. During recovery, storage nodes are busy leading to high read/write latency. We implemented tunable recovery throttle rate to mitigate this impact. This reduce average latency during recovery by approximately 60%.
  • Bucket Sharding: Amazon S3 API specification requires objects to be bucketized. Ceph implements bucket as an object hosted on a single storage node. At our scale, the storage node that hosts the bucket becomes a hotspot, which we mitigated by implementing sharded buckets that are spread across multiple nodes.

Future Development

So far, we have tuned COS to a large Yahoo use-case, namely Flickr. However, other Yahoo use cases require object storage with different workload patterns and different tradeoffs. To make COS a widely used platform at Yahoo, we are addressing several enhancements in near to mid term.

  • Scale: We have already deployed an initial multi-petabyte solution. In 2015, we plan to grow this 10-fold or more to accommodate other use cases  such as Mail, Video, Tumblr etc. along with Flickr growth.
  • Geo Replication for Business Continuity: Currently, geo replication is carried out the application level. Ceph supports Geo-replication. However, we have not tested this capability for the scale and latency that Yahoo needs. We plan to scale and deploy geo-replication in COS.
  • Optimize latency for small objects: Many use-cases such as serving thumbnails and serving during image search have small objects of the order of a few kilobytes. We need to tune COS for these use-cases.
  • Lifecycle management: One of the big advantages of Software Defined Storage is the hardware, software choices for cost and performance tradeoffs. Automatic classification of  objects into hot, warm, and cold objects will allow us to take advantage of that flexibility and provide differentiated services.

By Narayan P.P.S, Sambit Samal, Satheesh Nanniyur

January 10, 2016


It was a shapeshifter… A very diabolical shapeshifter…

Between getting held up in the motel and a case of mistaken identity, today was a particularly rough day. The case is solved, however. No more bodies will go missing.

Sam somehow made it back to the bunker within the day. I am still under as to how we have yet to catch a speeding ticket, but at the same time we know not to take any major highways. Frankly, I believe we are all too drained to care at this point.

Coming back to the bunker, coming home, is a very rewarding experience. No matter how many days, weeks, or months, we are gone, the routine that is the route to the bunker somehow manages to stay consistent: Dean would go straight to the shower, Sam to the library to put away any lore books we brought with us, and I would busy myself with taking weapons or delicate objects to storage. Always the same, day in and day out. It’s very human that way.

But this case was a little different in reception. The shifter had somehow managed to morph into late hunters as well as ourselves. I believe the emotional toll was grating for Sam and Dean, even if neither will even attempt to discuss it. I know it took it’s turn with me when the shifter turned into Samandriel.

Hence the routine changed. Instead of our usual chores, Dean dragged me to sit on the couch in front of the television, Sam not far behind with beers. The rest of the night was spent in silence, the television playing yet another sports match, though my fatigue was too great to remember just what sport occurred. I have a feeling that this is Sam and Dean’s way of communication, this silent scene that I witnessed and partook in. The only sounds apart from the television came after about an hour when Dean’s stomach growled. Only then did any semblance of the routine begin to return. We are creatures of habit, after all. 

I sense that this case was only the beginning of a list of emotional events that neither Winchester has completely told me about. I suspect it relates to the Darkness somehow.

But enough is enough for now. Dean is making burgers (no surprise I admit) while Sam is putting the lore books away. The past is behind us now.



Yesterday | Tomorrow

Massus, rat-like ghouls that have invaded Zone 2’s mall. These portly creatures are very greedy, not to mention hostile. They will often steal from the mall’s storage and take these objects to their nests where they hoard them in a messy pile. They do not get along with the Gilles De Rais, who are only trying to keep the stock in order.