I was using Colab to run AlphaFold2 but only able to run 2-3 jobs per day. I thought if I purchased Colab Pro+ I would be able to run several jobs (notebooks) in parallel. However, when I open a second tab in my browser I only see the first job I started running. How can I start a second (as well as third, fourth, etc.) job so they run simultaneously?
Related
I'm not an advanced programmer.
I have a webapp in Google Appscripts where users use it to punch in and punch out their working hours. I have 5 setinterval functions that updates their hours every minute.
The 1st screenshot is from dev version where I'm the only user but the 2nd screenshot is from the prod version. (I've hid the function names)
As you can see in the 1st screenshot that the functions runs exactly every minute. But in the 2nd screenshot since it is shared with several users, it is triggered many times within a minute. This obviously increases the stress level of the app and it takes some time to process the request since there are already functions running several times a minute.
My questions:
Is there a solution where I could limit the executions to run only once per minute no matter how many users are actively using the app.
Will deploying the functions as a library and calling it in the webapp reduce the number of executions?
Dev version
Prod version
everyone!
Is there any way to link two Cron Jobs in OpenShift? I have two Cron Jobs. The first one makes a .tar archive from some data. And the second one should operate with this archive. Can I add some condition to the second Cron Job, to make it run only if the first one has finished? The first Cron Job can run from several seconds to several hours, so it is not very comfortable to guess certain time interval, to be sure that it is completed.
Will be thankful for any idea.
Share the archive file via persist volume, and in the second job readiness probe to check if the jar file exists, then make decision to go ahead or abort for next check, archive the archive file to other location after finish.
With Kubernetes API to schedule the second job in the first job
I'm probably going to word this poorly, but here goes.
I've created an SSIS Package with an email proceedure. It is supposed to send three emails, each one based on a SQL query.
The email tasks run sequentially, as part of the reporting requirement (An automated run is required daily, but sometimes one of the three emails needs to be sent manually. In those cases the other two Data Flow Tasks are disabled)
Heres where things get fishy. I can run the task from the editor, and no issues arise. Results: 3 emails, limited latency. These are relatively small queries (~50k records). When the task is run from Windows Task Scheduler, I get two of the three emails (notably the first two in the sequence), and quite a bit of latency (~10 minutes total execution, ~ 3 minutes between emails.) Latency isn't concerning me, but the missing email is.
The task is set to expire if it runs longer than 12 hours, so timeout is unlikely the cause. I'm tearing my hair out trying to figure this out!
Note: to make things more interesting, I recompiled the script executing all three email (script) tasks in one data flow task. Same behaviour there, with a very interesting twist. Every time I complied the bianries with three email tasks I got a two emails
Example:
Compile 1 -> Load into Windows Task Scheduler
Result -> Lab & IT email
Compile 2-> Load into Windows Task Scheduler
Result -> Base & IT email
The heck?
Users of my application need to be able to schedule certain task to run at certain times (e.g. once only, every every minute, every hour, etc.). My plan is to have a cron run a script every minute to check the application to see if it has tasks to execute. If so, then execute the tasks.
Questions:
Is the running of cron every minute a good idea?
How do I model in the database intervals like cron does (e.g. every minute, ever 5th minute of every hour, etc.)?
I'm using LAMP.
Or, rather than doing any, you know, real work, simply create an interface for the users, and then publish entries in cron! Rather than having cron call you every minute, have it call scripts as directed by the users. When they add or change jobs, rewrite the crontab.
No big deal.
In unix, cron allows each user (unix login that is) to have their own crontab, so you can have one dedicated to your app, don't have to use the root crontab for this.
Do you mean that you have a series of user-defined jobs that need executed in user-defined intervals, and you'd like to have cron facilitate the processing of those jobs? If so, you'd want to have a database with at least 2 fields:
JOB,
OFTEN
where OFTEN is how often they'd like the job to run, using syntax similar to CRON.
you'd then need to write a script (in python, ruby, or some similar language) to parse that data. this script would be what runs every 1 minute via your actual cron.
take a look at this StackOverflow question, and this StackOverflow question, regarding how to parse crontab data via python.
I use Hudson to automate the testing of a very large important product. I want to have my testing-hosts able to run as many concurrent builds as they will theoretically support with the exception of excel-tests which must only run one per machine at any time. Any number of non-excel tests can run concurrently, however at most one excel test at a time must run per machine.
Background:
Most of my tests are normal unit-tests - the sort of thing that I can easily run in parallel. Unfortunately a substantial and time consuming part of my unit-testing plan consists of tests which have been implemented in Excel.
You might think it crazy to implement a test in Excel - actually there's an important reason: Most of our users access our system via a Excel. Excel has it's own quirky ways of handling data so the only way to guarantee that our stuff works for Excel users is to literally implement our reg-test our application Excel.
I've written a test-runner tool which allows me to easily fire off a group of excel tests: Each test is a single .xls file. Each group is a folder full of excel files. I've got about 30 groups which need to be run for an end-to-end test. My tool converts the result of each of the tests into JUnit style XML which Hudson is able to understand. The tests use the pywin32com library to automate excel. When run on their own they are reliable.
I've got a group of computers which are dedicated to running tests. Each machine is quad-core and can theoretically run quite a lot of stuff at once. Unfortunately I've found that COM cannot be used to safely control more than 1 excel per machine at a time.
That is to say if a 2nd build stars which tries to talk to Excel via COM it might interfere with the one which is already running and cause both tests to fail.
I can run as many other non-excel processes as the machine will allow but I need to find a way so that Hudson does not attempt to launch any more than 1 process which requires excel on any one machine concurrently.
Sounds like the Locks and Latches plugin might help you.
http://hudson.gotdns.com/wiki/display/HUDSON/Locks+and+Latches+plugin
Isn't hudson java?
Since you've tagged this post python, I'll point out that buildbot, has slave locks to limit individual steps on individual slaves (or use them as more coarse locks if you'd like).