OCEAN "jobs" grinds to near halt....

Discussion in 'Cadence' started by phil, Sep 11, 2006.

  1. phil

    phil Guest

    I have an OCEAN script in a BIG for-loop that submits many jobs -
    looks a bit like this:

    foreach( corner process
    foreach( vdd voltage
    foreach( ctemp temperature
    foreach( vicm list(0.05 0.5 0.85 1.3)
    foreach( prc par

    /* other stuff going on */

    jobs=cons( run(?jobName job ?queue
    "hspice") jobs)

    )))))


    It all works fine and the HSPICE Q has about six jobs running at any
    one time (jobs are short - two minutes)......BUT after a while (maybe
    150 or so jobs) - the whole thing grinds nearly to a halt. I only see
    ONE job on the Q at any one time ????

    Any ideas please.....at a complete loss.

    Thanks.
     
    phil, Sep 11, 2006
    #1
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. "n" for "nea" (near)

  2. distributed jobs in ocean

  3. Multiple Batch Jobs but I need a common GUI

  4. any jobs in SanDiego?

  5. <jobs> CATIA, SMARTEAM

  6. Pro-E Jobs

  7. OT - SolidWorks design position near Plattsburgh, NY

  8. So near and yet so far . . .

Loading...