BOINC 8.3.0.6b
CNT Edition
Practical CNT variant manual BOINC 8.3.0.6b and DCBench 0.6.0-P6. Describes the competition functions, statistics, localization, color themes, buchmarks, comparison of performance and safe management of team results database.
What is different from the usual BOINC Manager
BOINC 8.3.0.6b CNT is a team Windows x64 variant over BOINC 8.3.0 base. Maintains standard BOINC operation and complements functions intended primarily for competitive counting, clearer work with projects, localized interfaces and custom color themes.
The results shall be recorded in the data sheet.
SOFT / HARD detention of finished work without the need to cut the project from new work.
Scrollable graphs
Separate project statistics are no longer crammed into a useless grid.
♪ The mes.boincm ♪
Optional color themes of the Manager loaded from an external data file.
CPU / GPU directly in Advanced View
NCPus, percentage CPU of cores, CPU of duty-cycle and experimental GPU of duty-cycle without interference with tact or power limit.
cc _ config.xml editor
Raw editor via GUI-RPC with validation, backup and instant read of the Core Client changes.
Safe No new task
NNT only stops getting more work; already accepted jobs, downloads, running, upload and report remain preserved.
0-600 s instead of fixed 180 s
Work-fetch lead can be set separately. 180 s retains upstream behavior, 10 s is practical for very short GPU tasks and 0 s means fetch up when the actual depletion of the stock.
33 languages of the Manager
The new texts 8.3.0.6b are explicitly supplemented across all the Manager catalogues; release audit now requires 33 × 56 = 1 848 translations.
New clear build workflow
DevKit development has a new recommended path in the folder WORKFLOW_8306B. The historical root CMD / BAT remains unchanged due to compatibility and 26 canonical BOINC scripts remain unchanged.
Environment
Check package and pre-requisites, VS2026 / v145, aperture and verification of pinned BOINC 8.3.0, vcpkg and localization tools.
BOINC + Manager
Local layers 8.3.0.4b → 8.3.0.5b → 8.3.0.6b, localization, Debug / Release build and staging.
DCBench + RRSim
DCBench dependencies / build / test and also upstream BOINC boincsim (RRSim), snapshot inputs and smoke test.
QA + release + AI
Audits, Windows runtime checklist, QA marker, promotion, ALL-IN-ONE runtime and package AI_AGENT_CONTEXT.
For a normal fresh build, it is not necessary to manually fit each interversion. Step 13 is cumulative and can attach the current 8.3.0.6b layer directly to the pure pinned source. Steps 11 and 12 are maintained for checking individual milestone states.
Detailed map is in DOCS\ WORKFLOW _ 01 _ 40 _ CZ.html. Release part is fail-closed: without the real Windows runtime PASS you cannot perform promotion.
The result bar - the main competition news
The bar is a per- project function for pre-counting. The objective is to: hold the results completed and release them at the right time, but at the same time do not block the reception of new work. Replaces gross blocking of the project server through, for example, hosts.
Normal operation
Upload and report work by default. The project acts like a regular BOINC.
Soft parentheses
Output files may be uploaded, but the finished result is not yet reported to the scheduler. The new job may continue to come.
Hard parentheses
The upload of the result files and the final report will be detained. The download of the new job remains allowed.
How do I know the barrier is active?
The state is visible on the button and in the column Condition. It doesn't make it necessary to remember where you turned the gates on - you can see it on the list of projects immediately.
Statistics: from the crammed grid to the readable scrolling
For an account with dozens of projects, the original "All Projects (separately)" mode reduced charts so, It's hard to use. The new option will show a smaller number of large graphs and make the rest available by scrolling.
Location of BOINC Manager and wider control panel
BOINC Manager 8.3.0.6b contains modified localization in all 33 languages manager available. Function texts Result and Colour Theme are translated across supported languages, so that these parts of the interface do not pass to English unnecessarily. At the same time, they are corrected by a material error translations where they could change the meaning of the settings.
The wider left panel
Panel Command / Project / Display is wider to take Czech and other longer localized names The buttons did not shorten the three dots unnecessarily. The buttons also use common BOINC tooltips with the function explanation.
Optional color themes over themes.boincm
If he's next door boincmgr.exe file ♪ The mes.boincm ♪, The manager loads from it available colour pallets and makes them available in the menu Display → Color theme.
| Token | Which typically affects |
|---|---|
| bg / fg | main background and text |
| table _ bg / table _ fg / table _ selected | List of projects, tasks and transfers |
| Button _ bg / Button _ fg | buttons and tag panel |
| status _ bg / status _ fg | lower status line |
| progress _ * | progress bars and their variants |
| accent / border | highlighting, active elements and frames |
More screenshots
All thumbnails are clicking. The image opens over the whole screen and can be closed by clicking outside the image, by crossing or by clicking the Escc key.
DCBench - databases and benchmark computers across BOINC projects
DCBench is a separate accompanying application to this BOINC devkit. It is not part of the BOINC Manager and does not change its database or the normal operation of the client. It is intended for Repeatable CPU / GPU power measurements, computer and user records, comparison of results, safe collection of results from team members and publication of audited database. The goal is to replace today's hand workflow "result on forum → manual transcription with admin → shared XLSX" a well-defined and auditable process.
CPU and GPU
CNT Benchmarks and project benchmark paws. Each test is tied to a particular binar, workload and validation rules.
SQLite + audit
The authoritarian MASTER database is separated from user working data and is digitally signed.
.dcbsub and XLSX
The user sends one package to the admin with all his PC and measurements. Admin publishes the audited XLSX snapshot.
Filters and cards
Asc / Desc settings, filters by team, user, CPU, GPU, project, ISA and other detailed views.
Main function DCBench 0.6.0-P6
BOINC host info and measurement
DCBench can load BOINC host information, display hardware / telemetry and monitor power and energy at the available provider. Unavailable telemetry is not recorded as false 0 W.
Compare Graphs + Revision Diff
New graphs through / power / energy and comparison of database revisions make it easier to find differences between results, machines and database release.
BOINC Slot Shim
For science applications that need BOINC runtime environment, local Slot Shim is prepared for reproducible benchmark without scheduler and without reporting the project's work.
Multilingual GUI + reliable .dcbsub
The interface supports ten language choices and submissions use controlled export / import with the detection of duplicit and admin approval.
9.1 Architecture: three separate worlds of data
USER.db
Local working database of the user. It contains its own computers, configurations, benchmark runs and prepared submissions.
EDITOPTIONAL LOCALMASTER.db
Official database of approved results. It only writes admin workflow. The usual application uses read-only.
APPROVED LOCKEDAudited XLSX
Public shared snapshot designed for Google Drive. It is simultaneously human-readable in Excel / LibreOffice and imported back to DCBench.
READ-ONLY IMPORT9.2 Workflow user → admin → Google Drive → other users
9.3 User application - what it can do
My Computers
The user records his physical machines and their configurations. One set can have multiple profiles - e.g. SMT ON / OFF, stock / ECO / PBO or different GPU settings.
| user _ uid | stable user identity |
| Machine _ uuid | stable identity of physical PC |
| config _ uuid | specific machine configuration |
| run _ uuid | one specific benchmark run |
User Card
Each User ID has its own profile with team, nickname, PC list, configuration and all approved results. The nickname can change, UUID remains the same.
Export: the complete card of one user can be exported to the XLSX itself.
Computer Card
Displays CPU, GPU, RAM, OS, configuration, benchmark history, performance, energy data and submission history. The repeated measurements shall be connected to the same machine instead of the setting of duplicity.
Local vs. Official result
The public audited database can be displayed in comparison with its own local results. Local / unapproved values are clearly marked and cannot be displayed as official MASTER data.
9.4 Arrange, filtering and comparison
The DCBench tables support the shift by clicking on the column header. First click in order ASC, second DESC, the next returns the starting order. Filters can be combined and the current filtered view can be exported.
Hardware
CPU vendor / model, number of cores / fibres, ISA, RAM, GPU, OS, architecture, driver and according to test also CUDA / OpenCL runtime.
Identity
Team, User ID, Nickname, Machine ID, name of the lineup, date of result and status of approval.
Benchmark
Project, applications, versions, benchmark pack, resource CPU / GPU, SCALAR / SSE2 / SSE3 / AVX and other project profiles.
9.5 XLSX exports
DCBench uses XLSX not only as a report, but also as a portable public snapshot database.
Normal export
- Complete Database
- Current filtered view
- Selected users
- Selected machines
- Selected benchmark
- User profile
Admin audited export
Admin can export a complete MASTER or only a selected audited subset. XLSX carries a database revision, active filters, number of records and data needed to verify integrity.
Typical workbook includes for example:
Type of power ratio SSE2 / Scarar, SSE3 / Scarar or AVX / Scalar are in export actual Excel formulas, not just precalculated text values.
9.6 Import of audited XLSX as read-only database
The user downloads the current audited snapshot from the Google Drive team.
The file will be moved to DCBench or selected in the Import / Open public database menu.
DCBench checks schema, revision, integrity and signature of inserted authoritative snapshot.
The data are opened as a public database. They can be filtered, sorted, compared and re-exported, but not edited.
9.7 Batch submission .dcbsub
One user does not need to send each test separately. Function Export Submission creates one package containing all selected measurements - for example several PC, multiple configuration and more project benchmark.
Admin can only drag the file to DCBenchAdmin. Known user _ uid with automatic connect with existing user; known Machine _ uuid with an existing PC. This limits the creation of duplicates caused by a change of nickname or manual transcription of computer name.
9.8 Admin workflow and STAGING
Admin drops one or more .dcbsub files to the administration version.
Pairing will take place with user _ uid, machine _ uid and config _ uuid with existing database.
Check the duplicate run UUID, benchmark pack authority, hash, validation output and obvious HW irregularities.
Admin sees VALID, DUPLICATE, WARNING, REVIEW REQUIRED and can approve, correct metadata, postpone or refuse individual items.
Approved records are entered into MASTER.db as APPROVED + LOCKED and a log audit is created.
A new revision, signature and audited XLSX / Release package for Google Drive is created.
If admin fixes the error in the manually entered metadata, the original value is not lost. Audit trail can keep submised _ value, approved _ value and the reason for change. The approved historical result is not rewritten "quietly '; the correction can be created as a new revision / superseding record.
9.9 Benchmark Packs .dcbpack - tests across BOINC projects
DCBench is not limited to one fixed benchmark. Project tests are packed as .dcbpack. Pack describes project, application, version, resource CPU / GPU, accurate binary, workload, arguments, validation rules and SHA-256 of all relevant files.
Asteroids
The reference CPU pack follows the historical CNT benchmark. The profiles x64 SCALAR, SSE2, SSE3 and AVX use a frozed workload and validated original binary.
RUNNABLE LEGACY COMPATIBLEPrimeGrid Genefer GFN16
GPU pack can be created from the current project binary already downloaded by local BOINC client. Capture builder fixes a specific version and its hash.
CAPTURE BUILDER NVIDIA / AMD / INTELOther projects
The same interface can be used for other BOINC CPU / GPU applications if reproducible task and correct output validation can be prepared.
PLUGIN FRAMEWORK| Part of the paw | Purpose |
|---|---|
| Project / App metadata | It clearly identifies the project, application and version. |
| Resource profile | CPU, NVIDIA GPU, AMD GPU, Intel GPU, OpenCL / CUDA and other properties. |
| Binaries | Science app and possibly DLL / kernels with SHA- 256. |
| Workload | Reference test bag and auxiliary data. |
| Runner | Working directory, command line, number of parallel tacks and other parameters. |
| Validation | Exit code, existence of output, SHA-256 or numerical tolerance. |
Pump confidence states:
TRUSTED LEGACY UNVERIFIED LOCAL
9.10 Standalone BOINC application vs. BOINC slot shim
Some BOINC science applications can be run separately over the prepared input draw. They use the mode STANDALONE_PROCESS. Others expect BOINC API, heartbeat, shaded memory, init _ data.xml or a saline environment. For such applications is reserved mode BOINC_SLOT_SHIM.
9.11 Legacy CNT PeriodSearch 2017B
The historical CNT test package is preserved in DCBench as a reproducible legacy profile. The original methodology triggers multiple separate single-thread workpieces simultaneously and the scheming leaves Windows. The Legacy Scheme therefore deliberately does not add affinity / NUMA optimization to change comparability with the old results.
9.12 Power and consumption measurement
DCBench saves not only the resulting mean, but also individual running samples. That allows us to find out later instability, trotting or one significantly slower task. For newer profiles, you can register mean, median, minimum, maximum, standard deviation and through-put.
Energy data shall be separated according to the measurement method. The value from the socket wattmeter is not the same as CPU Package Power or GPU Telemetry; therefore, the database must know measurement _ method and measure _ scope.
9.13 Safety of MASTER database
Read-only MASTER
A regular client does not have a workflow for direct entry of approved results into MASTER. The tests themselves remain in USER.db until admin approval.
Ed25519 signature
MASTER database / snapshot has SHA- 256 and digital signature. The public application only contains public key; private signature key is not included in the distributed Devkit / runtime.
Audit log
The Commit records the revision, the origin of the submission, changes and the approving admin. History is therefore not dependent on handwritten notes in the spread.
Duplicate protection
UUID and hash- based identity limit double import of the same run, same paw or duplicate machine.
9.14 Integration with BOINC 8.3.0.6b
DCBench is a separate accompanying application stored in ADDONS\ DCBench. It doesn't change the BOINC Manager or its database. For the identification of the host can use BOINC GUI-RPC and for compatible The science application is available BOINC Slot Shim, which creates the necessary local runtime environment without the scheduler.
Separated data
BOINC client, USER.db and signed MASTER.db are separated. Benchmarking does not interfere with the normal operation of the BOINC client.
BOINC host information
DCBench can load CPU, OS, memory and available coprocessor information directly from the BOINC client and use it to identify the machine.
9.15 Localization of DCBench 0.6.0-P6
DCBench uses gettext / wxWidgets localization with English source texts as safe fallback. The language can be selected in the settings; the option is saved and the change of interface will be displayed after the application restarts.
Localized are common user parts of GUI including menu, bookmarks, buttons, filters, dialogues, status messages, benchmark pack manager, administration, Hardware / Telemeters, Compare Graphs, Revision Diff and import / export workflow. Technical identifiers such as UUID, SHA-256, SCALAR / SSE2 / SSE3 / AVX, NVML, RAPL or machine-readable CLI keys they are deliberately unaltered.
9.16 Branding and About
Czech National Team is a default / reference team, not a hardcode application restriction. The CNT logo is used in UI and About dialog, while the database can also register other teams. About dialog contains DCBench version, build, author and links to author creation.
9.17 What DCBench Replaces in Today's Process
| Today's procedure | DCBench |
|---|---|
| Result handwritten to the forum | Structured run with UUID, HW metadata and raw samples |
| Admin manually rewrites values | Drag & drop batch .dcbsub |
| Risk of typo / bad CPU / GPU | Automatic HW profile + admin validation |
| Shared XLSX is also a working database | MASTER SQLite is an authority; XLSX is an audited public snapshot |
| No stable machine identity | user _ uid + machine _ uid + config _ uuid + run _ uuid |
| One fixed test | .dcbpack framework for multiple BOINC CPU / GPU projects |