mx/MX_Pmodule
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ccp4 README: BINARY.setup py-compile phase is also slow

Browse Source 
Byte-compiling the bundled Python env writes thousands of .pyc files on
network storage; whole install budget on Ra is about an hour.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
duan_j
2026-08-18 20:37:55 +02:00
co-authored by Claude Fable 5
parent 89a9c682fe
commit fcedf651b6
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ccp4/README.md
+5 -2
View File
@@ -48,8 +48,11 @@ hand-downloaded tarball into the distfiles dir under the `name:` given in
The `install` step untars 3.7 GB into ~15-20 GB of small files on shared The `install` step untars 3.7 GB into ~15-20 GB of small files on shared
/opt/psi storage: the tar alone runs 10-30 min with no output (gzip is /opt/psi storage: the tar alone runs 10-30 min with no output (gzip is
single-threaded, small-file creation on network storage is the single-threaded, small-file creation on network storage is the
bottleneck), and `BINARY.setup` afterwards walks the whole installation bottleneck). `BINARY.setup` afterwards is just as bad — it walks the
for several more minutes. Watch progress from a second shell: whole installation patching paths and then **byte-compiles the bundled
Python environment** ("compiling py-files"), thousands of tiny .pyc
writes on network storage; expect another 15-30+ min. Budget roughly an
hour for the whole install on Ra. Watch progress from a second shell:
```bash ```bash
watch -n 30 'du -sh /opt/psi/MX/ccp4/9.0/' watch -n 30 'du -sh /opt/psi/MX/ccp4/9.0/'