New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
If the bot only shares the links to those files, it's not going to consume much bandwidth, unless you intend to host the bot and the files on the same server. Is that the intent?
They are using Equinix in Amsterdam, Miami and Singapore.
I saw some providers in the offer section, like Roayl Host / Royal Hosting, and their resellers. I recently saw a reseller.
@oplink $5/month plan has 50TB monthly bandwidth
https://my.oplink.net/store/amd-ryzen-3900x-vps/2gb
PS — make sure you follow telegram api guidelines
Check out our High storage VPS's
https://my2.dataideas.com/store/intel-xeon-storage-vps-shared-cpu
https://my2.dataideas.com/store/intel-xeon-storage-vps-dedicated-cpu
or even our AMD Ryzen 7 dedi starting at $39.99/m
https://my2.dataideas.com/store/dedicated
We don't meter bandwidth traffic.
for direct link bot, even a 512 mb, 5gb, 1 core server with even 1 TB/month will be more than enough.
I would say $11-$12 per year cheap vps will do the job.
Not for a public bot with many users
Define "many" . What's the range?
This is one such bot I guess.
I asked because the predecessor of Rose bot; "Marie" used to run on this same configuration IIRC (except a bit higher storage). The limit it faced was with regards to the database because in case of marie bot or rose bot, it's not only file links but different groups saves thousands of quoted message IDs each day.
The bottleneck was indexing the database due to which, queries were getting slow and the bot was re-written later. This occured when it had around million users.
If your bot is bogged down, then issue will probably be in the architecture of your app and your database design. Even a cheap node server can handle thousands of request concurrently without much stress.
If it's for a simple filtering bot (usually Marie clone for indexing stuff and responding with it), then yes, a server with a cheap configuration can handle it. But from the OP's requirements (high traffic/bandwidth), it seems the bot will also use the server to download files, generate links, and serve the files. A cheap server can't handle that for a few hundred users, let alone thousands.
We offer bot hosting using WISP