Opened 17 years ago

Closed 16 years ago

#5 closed defect (fixed)

jobmond unable to handle huge amount (3000+) of jobs properly

Reported by: bastiaans Owned by: bastiaans
Priority: normal Milestone: 0.3
Component: jobmond Version: 0.2
Keywords: Cc:
Estimated Number of Hours:

Description

When the amount of jobs in the batch passes 3000+, only partly a fraction is reported by jobmond (and displayed by the web frontend)

Change History (6)

comment:1 Changed 17 years ago by bastiaans

  • Owner changed from somebody to bastiaans
  • Status changed from new to assigned

comment:2 Changed 17 years ago by bastiaans

  • Milestone changed from 0.2 to 0.3

comment:3 Changed 16 years ago by bastiaans

Perhaps I need to incorporate duration detection in jobmond of injecting gmetrics.

Whenever it takes longer than the polling interval to inject all metrics, it should automaticly increase the interval temporarily.

comment:4 Changed 16 years ago by bastiaans

  • Milestone 0.3 deleted
  • Summary changed from jobmond doesn't handle large number of jobs properly to jobmond unable to handle huge amount (3000+) of jobs properly
  • Version 0.1.1 deleted

comment:5 Changed 16 years ago by bastiaans

now that native gmetric support is implemented, this bug may be fixed as a result.

need to test this now.

comment:6 Changed 16 years ago by bastiaans

  • Milestone set to 0.2.1
  • Resolution set to fixed
  • Status changed from assigned to closed
  • Version set to 0.2

I have not seen this occur anymore, so for now I'm assuming this issue is fixed.

Especially with the native gmetric support, jobmond is now faster then ever.

Note: See TracTickets for help on using tickets.