mirror of
https://github.com/yacy/yacy_search_server.git
synced 2026-07-30 12:14:36 -04:00
Michael Peter Christen
50 lines
1.8 KiB
Markdown
50 lines
1.8 KiB
Markdown
---
|
|
page: htroot/PerformanceConcurrency_p.html
|
|
help: help/PerformanceConcurrency_p.md
|
|
title: Performance of Concurrent Processes
|
|
package: monitoring-performance
|
|
access: admin
|
|
kind: admin-page
|
|
backend_java: source/net/yacy/htroot/PerformanceConcurrency_p.java
|
|
---
|
|
|
|
# Performance of Concurrent Processes
|
|
|
|
## Purpose
|
|
|
|
Concurrent Process Performance shows and tunes parallel work.
|
|
|
|
Use it when crawling, indexing, or search competes for CPU and threads.
|
|
|
|
## What You Can Do Here
|
|
|
|
- Concurrent Process Performance shows and tunes parallel work.
|
|
- Filter or limit the view to the symptom being investigated.
|
|
- Use the observation to decide the next crawler, index, network, or configuration action.
|
|
|
|
## Page Architecture
|
|
|
|
Monitoring pages read live peer state from queues, logs, network tables, memory counters, or process trackers. They are safest when used first as observation tools and only then as entry points to tuning pages.
|
|
|
|
## Correct Use
|
|
|
|
Use monitoring pages as evidence, not as guesses. Capture the current state, then connect it to the user-visible symptom: slow search, missing documents, stuck crawl, memory pressure, network isolation, or unexpected access.
|
|
|
|
## Access And Safety
|
|
|
|
Administrator access is required. YaCy protects `_p` pages as administration pages.
|
|
|
|
## Automation And API
|
|
|
|
Page backend: `source/net/yacy/htroot/PerformanceConcurrency_p.java`.
|
|
|
|
No request parameters are needed for normal use of this page.
|
|
|
|
## What To Expect
|
|
|
|
Expect observations: counts, logs, queues, timing, network rows, thread states, or resource values. Monitoring does not fix the issue by itself; it points to the next page or setting to change.
|
|
|
|
## Related Pages
|
|
|
|
- Related diagnosis usually continues on the status page, log viewer, performance pages, connection tracker, queue monitor, or network view.
|