Need Help?

Search our documentation and community forum

Terra is a cloud-native platform for biomedical researchers to access data, run analysis tools, and collaborate.
Terra powers important scientific projects like FireCloud, AnVIL, and BioData Catalyst. Learn more.

Understanding and controlling cloud costs

Follow

Comments

7 comments

  • Avatar
    breardon

    Allie Hajian, this is an amazing article and should be required reading for any new users on Terra. Well done! To that end, do you know if there is any word of Terra supporting many of the wonderful features that you mentioned such as regional / archival storage or intermediate file clean up? 

    0
    Comment actions Permalink
  • Avatar
    Allie Hajian

    breardon Thanks for the positive feedback! Note that this content came from our amazing Verily partner, Matt Bookman. I followed up on your questions; the good news is that the two features you mention are definitely on the Terra team's radar: in-app functionality for intermediate file cleanup is in active development (2020 Q1), and regional/archival storage is on the lower priority list (late 2020 at the earliest). For breaking news about when things happen, make sure to check in weekly with release notes. Sometimes changes happen so quickly even the comms team feel like we're playing catch up with new features!

    0
    Comment actions Permalink
  • Avatar
    lck

    I'm struggling a bit with understanding and controlling our costs -- starting in April, a big chunk of our costs (~20%) began to go to "logs ingestion." I would love some advice about how I can control this. I don't have the proper permissions to create logging exclusions, apparently, and I'm having a hard time figuring out what to do. This wasn't in our estimated budget for the project I'm working on, which is causing some trouble. Would appreciate any help or pointers to support resources for someone who is definitely NOT a Google Cloud expert! Thank you.

    0
    Comment actions Permalink
  • Avatar
    Allie Hajian

    lck This sounds frustrating! Your best bet is to email support@terra.bio and open a support ticket for this. 

    0
    Comment actions Permalink
  • Avatar
    Leonhard Gruenschloss

    Is there any way to select the cloud region that Terra is using to bring up GCE instances? It might be worth mentioning in case that's hardcoded to be us-central1. You mention the GCS egress costs, but those are hard to predict without knowing how those transfers will happen.

    (I just got surprised to find out that 300 GiB of egress between Australia and the US cost $50 for a non-workspace bucket I used for input data.)

    0
    Comment actions Permalink
  • Avatar
    Jason Cerrato

    Hi Leonhard Gruenschloss,

    The default region for workflows if none is specified is indeed us-central1. You can read more on the defaults and setting a specific zone for your runtime here: https://cromwell.readthedocs.io/en/stable/RuntimeAttributes/#runtime-attribute-descriptions

    For additional information, Terra workspaces buckets are located multiple regions in United States. You should be able to run workflows in non-US regions, but you would have to take any associated charges writing from/to the US bucket into consideration.

    I hope this helps!

    Kind regards,

    Jason

    1
    Comment actions Permalink
  • Avatar
    Leonhard Gruenschloss

    Thanks a lot, Jason, that's very helpful!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk