Skip to content

Removed vllm #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
srugano wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Removed vllm #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a560715
Removed vllm
srugano Sep 2, 2025
0408259
Requirements without GPU
srugano Sep 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions packages/postgresql-pgml/release.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,14 +72,14 @@ build_packages() {
$(package_name ${pg} ${ubuntu_version} ${ARCH})

# Upload to S3
deb-s3 upload \
--visibility=public \
--bucket apt.postgresml.org \
$(package_name ${pg} ${ubuntu_version} ${ARCH}) \
--codename ${codename}
#deb-s3 upload \
# --visibility=public \
# --bucket apt.postgresml.org \
# $(package_name ${pg} ${ubuntu_version} ${ARCH}) \
# --codename ${codename}

# Clean up the package file
rm $(package_name ${pg} ${ubuntu_version} ${ARCH})
#rm $(package_name ${pg} ${ubuntu_version} ${ARCH})
done
}

Expand All @@ -97,4 +97,4 @@ else
for ubuntu_version in "${!ubuntu_versions[@]}"; do
build_packages "$ubuntu_version" "${ubuntu_versions[$ubuntu_version]}"
done
fi
fi
3 changes: 0 additions & 3 deletions pgml-cms/blog/serverless-llms-are-dead-long-live-serverless-llms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,6 @@ Because we’ve curated the best in class models, they will always be instantly

Your application can instantly burst usage to massive scale without a second thought, other than the aforementioned cost of GPU usage. Financial costs are now the limiting factor, but we have an additional new lever to optimize costs even further.

### Multi-tenant continuous batching
It’s not just loading the model weights into GPU RAM the first time that’s expensive. Streaming those weights from GPU RAM to the CUDA cores for each request is actually the bottleneck for most LLM applications. Continuous batching allows us to reuse a single layer of weights for multiple different queries at the same time, further reducing costs, without significantly impacting overall latency. Thanks to vLLM team for [this impressive breakthrough](https://arxiv.org/abs/2309.06180) in performance.

### Simplified pricing
Compared to using a host of services to provide comparable functionality, our pricing is significantly simpler. We charge for:

Expand Down
Loading