General review of rate section

[hkershaw-brown]

General comments on the rates page. I think this page needs a good proof read/rewrite, here are a few things I noticed

• The posted rates aren't available on Oscar.
• The + used for Plus accounts and the + used for footnotes look similar.
• Free exploratory accounts are available to everyone at Brown, not just faculty and PIs
• "priority accounts will have faster job start times" is kind of an imprecise thing to say. The jobs have a higher priority.
• The ++ footnote is on the GPU Priority High End but it doesn't relate to GPUs
• I think scratch is purged more often than every 30 days. The correct info is "files older than 30 days are purged"
• It is not clear here that file storage rates are for Isilion and Oscar.
• Probably too late for this, but the names of the different accounts are really easy to get confused "HPC GPU Priority Standard+" ? Maybe names that are less easily confused "Bronze, Silver, Gold" or something like that. Why do some of the names have HPC in them? The Exploratory accounts are using the same cluster.
• Possibly some way of visually representing the accounts vs a comparison table. Area for core hours, color for GPU type
• CPU "intensive" seems like the wrong word here. More cores and CPU intensive aren't the same thing. "Basic GPU intensive" ? What does this mean?

[hkershaw-brown]

The actual correct info on purging:
"files that have not been accessed for more 30 days are purged"

[mirestrepo]

@hkershaw-brown @mttunca who has the knowledge/language to review that section. Who wants to take the lead?

[fernandogelin]

@hkershaw-brown There were some changes to the rates page, did they address the issues you brought up here or should we keep this issue open?

[hkershaw-brown]

@fernandogelin I would keep this issue open. It looks like there are still many problems with this page, e.g:

• "Exploratory (PI Sponsored) | 32 for 48 hours per job" is incorrect right? The limit is across all your jobs. There is no info on how much memory you get. There is nothing about purchasing a condo (can you still do this? I don't know). I don't think these advertised rates actually match what is in the slurm associations on Oscar.

• The condo price does not have a /time. e.g. is it $10,000/day? $10,000/million years?

• The quota is wrong I think too. 256G (should be GB) is now a 1TB, but it is per group not per account. Isn't that the new policy?

• I think the scratch purge is run more often than every 30 days. For users, it is more important to know which files will be purged - files with an access time greater than 60(?) days ago.

TL;DR this should go to back to Oscar management for policy review

[fernandogelin]

@hkershaw-brown thank you! I'll bring this up during the triage meeting tomorrow.

[hkershaw-brown]

Good luck @fernandogelin !

[kubatarlowski]

Hi,

I just made a pull request for this. I also originally pushed using git push instead of npm run push, so there is a branch called content-rates that can be deleted. The correct branch is content-rates-correct.

Thanks,
Kuba

[fernandogelin]

Hi Kuba, `npm run` is just for committing, to push you just do `git push`, there's no `npm run push`. Fernando

…

On Fri, Jan 31, 2020 at 10:30 AM kubatarlowski ***@***.***> wrote: Hi, I just made a pull request for this. I also originally pushed using git push instead of npm run push, so there is a branch called content-rates that can be deleted. The correct branch is content-rates-correct. Thanks, Kuba — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/brown-ccv/ccv-website/issues/134?email_source=notifications&email_token=AAXKMBASS35KPMN2JHU3PWLRAQ72NA5CNFSM4JVSUSMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKPABAY#issuecomment-580780163>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXKMBHKDWDKKFHM3S47H3TRAQ72NANCNFSM4JVSUSMA> .

-- <http://ccv.brown.edu/> Fernando Gelin <https://github.com/fernandogelin> <http://directory.brown.edu/uuid/8144f0fb-0d36-47ed-ae64-ab07c232ebba> *Senior Research Software Engineer* Data & Visualization Center for Computation and Visualization Brown University | CIS

[kubatarlowski]

my mistake, I meant npm run commit. I did a regular git commit -m and then pushed that branch under "content-rates"

[fernandogelin]

@mttunca @singhsaluja were these issues addressed in the latest changes to the rate section? Can this be closed?

[mttunca]

@fernandogelin - we think this can be closed. Closing.

[hkershaw-brown]

This still doesn't seem correct. Is there a Max Wall time for jobs of 96 hours? This doesn't match the footnote, e.g. a 104-core job to run for 160 hours.

[hkershaw-brown]

Is there a document somewhere which details what the account limits are supposed to be and what the slurm associations are. The website doesn't match what is on Oscar so it really confusing for users.