Does Typesense cloud have SSDs or HDs?
# community-help
a
Does Typesense cloud have SSDs or HDs?
j
SSDs
There's another special type of SSD called NVMe SSDs which is an option when you have a high availability instance (called high performance disk)
a
small thing, might want to consider updating the text/copy where it says “Regular Disk” under configruation
to say SSD
any idea on how much NVME impacts performance for typesense? its already pretty fast sub 25ms results
j
Ah, good catch. Will update that
k
I think for datasets where the doc size is small, the performance difference will be negligible.
j
Perf improvement will depend on the dataset and the number of fields in each document
k
I/O is not typically the bottleneck for Typesense. CPU is.
👀 1
a
Is there a way I can calculate the resources needed for typesense? I’m considering launching a user-facing feature that will interface with typesense directly and don’t know what i will need
also - is it possible to obfuscate the “url” on the client side and/or the key, or is that not needed/security theater?
j
If you can share the number of records, approximate size of each record and estimated traffic per day, I can help estimate
a
~20k total records, across ~4 collections ~1k users per day maximum education based, searching for questions mainly
j
also - is it possible to obfuscate the “url” on the client side and/or the key, or is that not needed/security theater?
It's fine to expose both of these publicly... They're designed that way.
a
of course i understand that - but is it possible?
j
Yeah a few users put the hostnames behind Cloudflare for eg for DDOS protection for eg
a
doesnt that have a sizable or material hit on network performance?
or is that a tradeoff for security/reliability
if you guys have any documentation on that would appreciate. thanks
j
It's a tradeoff... But it's not too big a hit from what I saw in my benchmarks. Cloudflare also keeps persisitent connections open to origins, so that helps minimize impact
1
If you search this Slack for Cloudflare, you'll find instructions on how to set this up
🙌 1
~20k total records, across ~4 collections
~1k users per day maximum
And size of each record?
a
~60-240 characters for the main searchable attribute
j
Ah ok, that's a total dataset size of ~5MB. Typesense usually takes 2-3x memory, so that's 15MB of RAM worst case to index that data, which is well within the 512MB RAM config. 2vCPUs should be more that sufficient to handle 1k users per day.
The only think to be aware of is that the base config (512MB RAM, 2vCPU) has a burst time of 1 hr every 24 hours. Meaning if any operation (search / indexing) pegs CPU for 1 hour, it will get throttled for the next 24 hours and then it resets.
If that's not preferred, then you want to pick a non-burst vCPU config
1
a
Do you guys have plans for dedicated CPU core instances?
k
We already have them.
a
okay will look into them further - thanks
the lowest dedicated cpu config starts at 115 per month, correct?
k
Correct but the burst CPU provides cumulative dedicated cpu that might just be fine for many apps. It's only an issue if cpu pegs at 100% totally until credits expire.
E.g. 2 gb ram / 2 vcpu burst option provides upto 4 hours of dedicated burst capacity. If your basline cpu load is only 15-20% that's enough for whole day. This will be a function of concurrent searches per second.