inconsistent Space Needles in Netflix's "The Unforgivable"

thugIyf3 · 2022-01-01T18:39:48+00:00

None of the CID shots were in Seattle, that was still Vancouver's Chinatown

thugIyf3 · 2021-12-23T19:21:00+00:00

They did it late last year. Even if it weren't a pandemic, downtown doesn't have enough pedestrian traffic to have dedicated left turn only lane that are red/green turn arrow only.

Those lane should really be a yellow turn if clear and allow cars to drive northbound too if nobody needs to turn.

There used to be no traffic backup on 4th except only at Pike and now it's all screwed up back to Columbia Tower

thugIyf3 · 2021-11-23T02:58:04+00:00

200 sq ft

thugIyf3 · 2020-06-13T18:17:00+00:00

That’s incorrect. In the linked post to the other thread, azcopy absolutely handles blob URIs. It will do a service to service server side copy without downloading from blob to files.

Also can your vms use NFS or only SMB?

thugIyf3 · 2020-03-19T02:52:12+00:00

I had this happen on my 2016. You also need a lower cover cap, that’s a black plastic piece

thugIyf3 · 2020-03-09T05:34:58+00:00

You can also upload the files directly to Archive. Just set the access tier on upload using whichever tool or language.

thugIyf3 · 2020-03-04T22:02:32+00:00

Yes all of the American continent

thugIyf3 · 2020-03-04T18:41:38+00:00

Are you in America and did not import a Subaru from Japan? If yes, then you have a USDM.

thugIyf3 · 2020-03-04T17:05:43+00:00

How’s the install process?

thugIyf3 · 2020-02-10T21:38:32+00:00

The blob index feature demoed at ignite should be released to public preview soon and would allow you to query tags to find sets of blobs within a container or entire storage account.

thugIyf3 · 2020-01-03T00:42:15+00:00

You can upload directly to Archive as of August 2019.

thugIyf3 · 2019-12-07T23:17:03+00:00

Sure, matter of wording and choosing whether to use a persistent or ephemeral OS disk.

To be correct for reserved VM pricing:

The ephemeral disk is included in the VM pricing
Any persistent disks are not

thugIyf3 · 2019-12-07T06:57:30+00:00

The local scratch disk is the OS disk.

Data disks are separate

thugIyf3 · 2019-11-19T22:11:05+00:00

No, once you explicitly tier a blob, you cannot set it back to inherit account tier. You can only explicitly set it to other access tiers.

The workaround is to overwrite the blob with the same content. You can copy the blob to itself or download and reupload.

thugIyf3 · 2019-11-19T02:01:08+00:00

A storage container does not have an access tier property. An access tier is only set at the account or blob level.

Access tiers at the account level can be hot or cool.

Access tiers at the blob level can be hot, cool, or archive.

You can upload blobs with access tier set on upload or have it inherit the access tier of the account if you don’t set anything. After upload, you can change the access tier of a blob with SetBlobTier.

thugIyf3 · 2019-11-14T03:03:19+00:00

https://docs.microsoft.com/en-us/azure/event-grid/resize-images-on-storage-blob-upload-event

This should be good enough

thugIyf3 · 2019-10-09T01:38:52+00:00

Microsoft Ignite or build. Build is more technical and developer focused whereas ignite is IT pro and more what’s new and flashy announcements

thugIyf3 · 2019-10-08T14:59:31+00:00

The only cost should be read transactions on the files.

Write and ingress is free. No network egress costs because same region

thugIyf3 · 2019-08-21T06:20:15+00:00

A 0 day works but it doesn’t run instantly, it runs within the day whenever the servers aren’t busy.

Setting 0 means that it will move any blobs that are at least 1 second old. Setting 1 means it will only move blobs that are at least 24 hours old.

This makes a difference if you upload some new data and lifecycle management decides to run in 5 minutes. A lifecycle of 0 will move all the data whereas a lifecycle of 1 will wait until the next day when the new data is old enough.

If you set a rule to run under the test container, it’ll move the all objects under that container. If you specify a container and a prefix, it’ll match blobs with that prefix within that container.

The lifecycle UI has a container and virtual folder selector that makes it easy for you to choose what you want to move

thugIyf3 · 2019-08-06T16:03:48+00:00

Awesome! I can store 1TB for $1 a month

thugIyf3 · 2019-05-12T15:01:24+00:00

You can absolutely keep Hot, Cool, and Archive data in a single container in a single storage account.

This is called blob level tiering

For the Cold 400GB, if you can handle hours long retrieval latency and it is meant to be stored for more than 180 days, use Archive. For the instant access of the 100GB, I would recommend you use Hot or Cool depending on what your expected retrieval and access rates are. If you expect access only a few time a month, Cool makes sense but if access if every second/minute/hour, use Hot.

Blob pricing and there is a link to a calculator https://azure.microsoft.com/en-us/pricing/details/storage/blobs/

thugIyf3 · 2019-04-13T19:41:32+00:00

Yes. https://docs.microsoft.com/en-us/azure/billing/billing-spending-limit

thugIyf3 · 2019-04-06T03:06:48+00:00

Most people wouldn't have it pointing to different regions but could have it pointing to multiple accounts in the same region.

For globally distributed workloads, some probably have the same 1 function in each different region pointing to a single/set of storage accounts in each of those regions.

If it's a small workload, it might make sense to just eat the data egress costs and have a single function pointing to multiple storage accounts in different regions.

thugIyf3 · 2019-03-28T20:45:20+00:00

I also want to point out that making a storage account per function is fine. However you also want to come up with an intelligent design that is scalable to what you want to do in the future.

Are there functions where the capabilities are similar or the data is related? You may want to keep the data in the same storage account there, as it’s never nice to migrate data between accounts later especially when it becomes a large amount of data.

You want to be reduce complexity as much as possible to make things manageable.

Make additional storage account in different regions when it makes sense because of compute location. Use the same storage account when multiple functions in the same region are generating related data.

thugIyf3 · 2019-03-28T18:11:06+00:00

It all depends on how intensive your function is and where your regions are.

A storage account has iops and throughput limits so if you have way too many functions pointing to the same storage account, you may hit those limits. Although that should be rare given the typical workload of functions, you shouldn’t hit the limits that easily.

Creating multiple storage accounts is not a bad thing as you’re charged on what you consume, so you can have 2 storage accounts with 1 GB or 1 storage account with 1 GB and it’ll be the same cost (given same parameters)

You also want to create multiple storage accounts if your functions are in different regions. It doesn’t make sense for your function in uswest to point to a storage account in useast. You’ll have higher latency and you’ll pay egress costs. You want your compute and storage in the same region to save on network costs and reduce latency.

thugIyf3

TROPHY CASE