I'm pretty sure I've been getting pods where "/" lives on a network disk
Which makes data reading impossible and the pod useless.
I have a little 'see how fast you can read the database' script: It does 6000 iterations/second in my home machine, reading from an SSD. It gets something like 600 iterations/second in "normal" pods, reading my data from /. If I try to read my data from a network storage it gets 2 (!!) iterations per second.
This pod which I just closed cause I don't enjoy paying for useless things also got exactly 2 iterations per second while reading from /. Exactly as if the / exists on the network instead of in the machine itself.
RunPod Pytorch 2.1 ID: wx3xh0bel2o00d 1 x A100 SXM 80GB 16 vCPU 250 GB RAM runpod/pytorch:2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04 On-Demand - Secure Cloud This is unacceptable.
I have a little 'see how fast you can read the database' script: It does 6000 iterations/second in my home machine, reading from an SSD. It gets something like 600 iterations/second in "normal" pods, reading my data from /. If I try to read my data from a network storage it gets 2 (!!) iterations per second.
This pod which I just closed cause I don't enjoy paying for useless things also got exactly 2 iterations per second while reading from /. Exactly as if the / exists on the network instead of in the machine itself.
RunPod Pytorch 2.1 ID: wx3xh0bel2o00d 1 x A100 SXM 80GB 16 vCPU 250 GB RAM runpod/pytorch:2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04 On-Demand - Secure Cloud This is unacceptable.
0 Replies