question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

documentation: explanation / context of the "STAT" column in plotman status

See original GitHub issue

some explanation / context around the plotting statuses would be helpful and likely prevent further issues from being filed:

$ plotman status
 plot id    k           tmp            dst   wall   phase    tmp    pid   stat    mem   user    sys   io
d100ec50   32   /chia-plot1   /chia-buffer   1:14     1:5   175G   2551    SLP   4.9G   1:39   0:03   2s
dafd1a46   32   /chia-plot0   /chia-buffer   1:44     1:7   173G   1987    SLP   4.7G   2:25   0:05   2s

reference: https://github.com/ericaltendorf/plotman/issues/199#issuecomment-830617370

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

7reactions
Monstarulescommented, May 8, 2021

@piotrkochan commenting with code from this repository isn’t the answer to this question. There’s more to it than that. The actual question was in regards to what the different statuses mean, and how to make them clearer, as mentioned in #199 . After reading the documentation of psutil, Chia, Plotman, and Linux status codes, I’m going to attempt to take a stab at possibly providing some insight:

RUN The process is currently running, meaning that it is reading and or writing data to the disk. Self explanatory.

SLEEP The process itself is asleep, as it is not reading or writing data to the disk. Chia in general will call several other processes when making a plot. It is not uncommon for a few processes to be in a standby mode, especially the actual “plot” process, of which the status we see in Plotman. Status SLP does not mean that your plotting has stopped.

DSK The disk itself is asleep and not running. Most disks will power themselves down by default, unless they are special kind of disk like the ones used in servers (Enterprise types). This can be rectified for normal disks by making edits to disk power options, I believe that it is under a utility known as “hdparm”, where you edit the amount of time it takes between no read/write and disk sleep. Unlike the SLP status, this one typically does mean that you are not plotting anything.

STP The process is stopped. You are not plotting at all. This one is pretty self explanatory.

3reactions
piotrkochancommented, May 7, 2021
        if status == psutil.STATUS_RUNNING:
            return 'RUN'
        elif status == psutil.STATUS_SLEEPING:
            return 'SLP'
        elif status == psutil.STATUS_DISK_SLEEP:
            return 'DSK'
        elif status == psutil.STATUS_STOPPED:
            return 'STP'
        else:
            return self.proc.status()
Read more comments on GitHub >

github_iconTop Results From Across the Web

XLIFF 1.2 Specification - OASIS Open
This document defines the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it...
Read more >
Examining Multiteam Systems Across Context and Type
To our knowledge, this is the first study to also examine how key MTS attributes (boundary status, goal type) influence MTS processes and...
Read more >
NEVADA - Federal Motor Carrier Safety Administration
Instructions for all tables in this section: Complete the tables below to document the State's past performance trend analysis over the past five...
Read more >
Scott - NYU Law
79, that courts do NOT look to the value of the consideration, only look at its sufficiency. Plowman v. Indian Refining Co. Defendant...
Read more >
ARTICLES - Hofstra Law
Richard A. Bales* & Jason N.W. Plowman**. ABSTRACT. Federal and state reporters are filled with examples of lopsided arbitration agreements drafted by ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found