yekta
RRunPod
•Created by yekta on 9/8/2024 in #⚡｜serverless
Problems with serverless trying to use instances that are not initialized
6 replies
RRunPod
•Created by yekta on 9/8/2024 in #⚡｜serverless
Problems with serverless trying to use instances that are not initialized
6 replies
RRunPod
•Created by yekta on 9/8/2024 in #⚡｜serverless
Problems with serverless trying to use instances that are not initialized
It also keeps redownloading these images on containers that are supposedly "running" quite often so it becomes pretty unusable
6 replies
URGENT! Network Connection issues
The blacklisting of the ID wouldn’t work in this case btw, because this particular provider of 4090s had the same problem on all machines probably (I tried 3 different one). If it was a list, I could simply deduct the “owner” based on machine specs and location (since all of them were matching).
157 replies
URGENT! Network Connection issues
Given the inconsistency of community instances anywhere (RunPod, Vast etc), I’d consider this a must have. Because otherwise a bunch of users will get served broken instances by RunPod itself (even though there are non-broken instances behind the scenes).
157 replies
URGENT! Network Connection issues
Negative list is also fine, however a dropdown is much simpler to implement and flexible since RunPod obviously already knows which instances are matching my criteria. It can simply list them and let me pick (if I want to, default can be autoselection still)
157 replies
URGENT! Network Connection issues
Vast lets you do this already. I get the upside of selection being so simple (you select 4090 and it’s done). However, I would rather have the option to be able to continue using the platform. Since I literally couldn’t pick a 4090 matching my criteria since RunPod kept selecting these broken set of instances on my behalf
157 replies
