hermanhugging commited on
Commit
52d3112
·
verified ·
1 Parent(s): 24407a9

Create DEPRECATED.md

Browse files
Files changed (1) hide show
  1. data/cif_models/DEPRECATED.md +112 -0
data/cif_models/DEPRECATED.md ADDED
@@ -0,0 +1,112 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # DEPRECATED
2
+
3
+ ## Why `data/cif_models` is deprecated
4
+
5
+ The previous approach based on storing datasets as large collections of small `.cif` files and performing preprocessing directly on an HPC cluster is strongly discouraged for several reasons:
6
+
7
+ ### 1. Inefficient I/O on HPC systems
8
+
9
+ HPC clusters are not optimized for workloads involving a large number of small files. Reading thousands (or millions) of `.cif` files leads to:
10
+
11
+ * High filesystem overhead
12
+ * Significant slowdown due to metadata access
13
+ * Poor overall I/O performance
14
+
15
+ ### 2. Reduced GPU utilization
16
+
17
+ Preprocessing performed on-the-fly during training:
18
+
19
+ * Continuously consumes CPU resources
20
+ * Creates a bottleneck between CPU and GPU
21
+ * Causes **low GPU utilization**
22
+
23
+ As a result, GPUs remain idle while waiting for data, which is highly inefficient.
24
+
25
+ ### 3. Impact on shared cluster usage
26
+
27
+ Because of the inefficiencies above:
28
+
29
+ * Jobs take longer than necessary
30
+ * GPUs are occupied for extended periods
31
+ * Other users must wait longer for access
32
+
33
+ This negatively affects overall cluster fairness and efficiency.
34
+
35
+ ### 4. Storage quota issues
36
+
37
+ During preprocessing:
38
+
39
+ * Each `.cif` file often produces one or more cache files
40
+ * Total number of files grows rapidly
41
+
42
+ For large datasets:
43
+
44
+ * `#cache files + #original cif files` can easily exceed SSD quotas
45
+ * This can cause job failures or require manual cleanup
46
+
47
+ ---
48
+
49
+ ## New approach
50
+
51
+ To address these issues, a new preprocessing pipeline has been introduced.
52
+
53
+ ### Key idea
54
+
55
+ Instead of processing `.cif` files on-the-fly:
56
+
57
+ * Preprocessing is done **once in advance**
58
+ * Results are stored in a small number of **LMDB files**
59
+
60
+ ### Supported datasets
61
+
62
+ * **QMOF** (originally `.cif`-based)
63
+ * **ODAC23**
64
+
65
+ * IS2R LMDB format
66
+ * Also includes `ODAC_init.tar` with `.cif` structures (compatible with QMOF-style preprocessing)
67
+
68
+ ### Output format
69
+
70
+ Each dataset/model combination produces:
71
+
72
+ * `*_train.lmdb`
73
+ * `*_val.lmdb`
74
+ * `*_test.lmdb`
75
+
76
+ This reduces:
77
+
78
+ * File count from millions → **2–3 files total**
79
+ * I/O overhead dramatically
80
+ * CPU preprocessing load during training
81
+
82
+ ---
83
+
84
+ ## Benefits
85
+
86
+ * Efficient sequential reads (LMDB)
87
+ * High GPU utilization
88
+ * Minimal CPU bottleneck
89
+ * No filesystem overload
90
+ * Avoids SSD quota issues
91
+ * Faster and more stable training
92
+
93
+ ---
94
+
95
+ ## Implementation
96
+
97
+ The new preprocessing pipeline is implemented in:
98
+
99
+ * The **latest version of the project code** (GitLab repository)
100
+
101
+ Preprocessed datasets are available in this repository under:
102
+
103
+ ```
104
+ data/lmdb
105
+ ```
106
+
107
+ ---
108
+
109
+ ## Recommendation
110
+
111
+ Do **not** use `data/cif_models` for training or preprocessing on HPC clusters.
112
+ Always use the preprocessed LMDB datasets instead.