10.46243/jst.2020.v5.i4.pp230-237 registered
Modular Microservice based GPU Utilization Manager with Gunicorn
Resolves to https://www.jst.org.in/index.php/pub/article/view/602
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2020.v5.i4.pp230-237
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 e34014bf1a716e20…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Modular Microservice based GPU Utilization Manager with Gunicorn (PrincipalTitle · en)
Published 2020-07-30
Part of Journal of Science & Technology · ISSN 2456-5660 · issue Volume 5 · pages 230–237
Agents
- Remya A. R (author)
- Suraj Kamal (author)
- Satheesh Chandran C (author) · ORCID 0000-0003-0728-0941
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2020.v5.i4.pp230-237
Abstract · en
:Graphics processing unit (GPU) is a computer programmable chip that could perform rapid mathematical operations that can be accelerated with massive parallelism. In the early days, central processing unit (CPU) was responsible for all computations irrespective of whether it is feasible for parallel computation. However, in recent years GPUs are increasingly used for massively parallel computing applications, such as training Deep Neural Networks. GPU’s performance monitoring plays a key role in this new era since GPUs serve an inevitable role in increasing the speed of analysis of the developed system. GPU administration comes in picture to efficiently utilize the GPU when we deal with multiple workloads to run on the same hardware. In this study, various GPUparameters are monitored and help to keep them in safe levels and also to keep the improved performance of the system. This study,
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2020.v5.i4.pp230-237 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Modular Microservice based GPU Utilization Manager with Gunicorn (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Remya A. R author: Suraj Kamal author: Satheesh Chandran C publisher: Longman Publishers published: 2020-07-30 part of: Journal of Science & Technology · ISSN 2456-5660 · no. Volume 5 · pp. 230–237 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2020-07-30 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
Recommended for a journal article and not in this record: the volume number.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 148 fields set · sha256 1ce4f1c6d140… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 21 Sep 2026, 07:31 | Metadata completed abstract (140 words) · licence | ● waiting for Crossref's answer | 7eeb1c80805c… |
| 21 Sep 2026, 07:53 | Read back: Crossref's record shows it | ● confirmed | 900ea7f37d8f… |
2 entries · the last fingerprint 900ea7f37d8fbac6251a574c56f3b262bd77c405ebf459afaf0691ceba48aecc · the history as JSON, each entry with the fingerprint before it, to check them yourself.



