You just need a unbreakable laptop like Lenovo Thinkpad T15 and some random HDD easy plug. Use EmEditor trial abuse tho

Stop posting shit when you don't know what you're talking about. It doesn't make you cool.

(March 27, 2022, 09:16 PM)Wild Wrote: You just need a unbreakable laptop like Lenovo Thinkpad T15 and some random HDD easy plug. Use EmEditor trial abuse tho

That would work if we are searching in 1 file only, not in all files at same time, something like HIBP

---

(March 27, 2022, 09:18 PM)thekilob Wrote: Stop posting shit when you don't know what you're talking about. It doesn't make you cool.

Thankyou for your feedback. Unfortunately I dont have time to read pink boi posts & chats

(March 27, 2022, 09:22 PM)HaxonGhost Wrote:

(March 27, 2022, 09:16 PM)Wild Wrote: You just need a unbreakable laptop like Lenovo Thinkpad T15 and some random HDD easy plug. Use EmEditor trial abuse tho

That would work if we are searching in 1 file only, not in all files at same time, something like HIBP

---

(March 27, 2022, 09:18 PM)thekilob Wrote: Stop posting shit when you don't know what you're talking about. It doesn't make you cool.

Thankyou for your feedback. Unfortunately I dont have time to read pink boi posts & chats

Kill yourself.

(March 30, 2022, 06:43 PM)Minori Wrote:

(March 27, 2022, 09:08 PM)HaxonGhost Wrote: I think many of us have atleast a TB of leaked data which few of us are still figuring out how to arrange them so it can be searched with no delays & with multiple strings

Here is my solution, please post your solutions, so it could be helpful to all.
1 best xeon processor with 64GB memory, SSD is best but HDD is okay for the data we have, so 18TB HDD is worth purchasing
Elasticsearch (tho its not database) using as database for its speed of search
Elasticsearch is horizontally scalable, means you can add more nodes to increase its capacity

Another option can be Apache Cassandra as its NoSQL but its searching feature is not good, so its not for our purpose

Please post with your solutions

1) What do you understand under "1 best xeon processor", first of all just because you know a server cpu brand doesn't mean you should use it for everything.

2) 64gb ram is, depending on your workload not enough. You need atleast 8 x 32gb ECC ramsticks and yes I understand everything I just said, try figuring it out without googling dumbass.

3) If you want it to be actually fast and not just caching everything in ram (which is still useful and recommended to do) you need to use nvme ssd's because hdd's are just not fast enough if you are searching through tb's of data.

1. Best Xeon CPU means its based on ones budget. If you can spend any amount, you can even go with Xeon Platinum 8280L
2. Its better for you to understand about elasticsearch first. As you are still a 12yr kid, it takes time for you to understand hardware requirements based on applications & budget allocation for hardware. You first need to be mature for all this, then understand why 64GB is better for elasticsearch.
3. NVMe SSDs are always better than SATA SSDs & SATA SSDs are always better than SATA HDDs. The main problem is, how much you invest for hardware which doesn't give any return. Be mature in finances KID.

Throw it in a NoSQL database and index it for speed. Handle parsing on the server to avoid redundant performance costs. Maybe spin up the back-end with actix-web if you want to get autistic.

(March 30, 2022, 07:01 PM)frydembrains Wrote: Throw it in a NoSQL database and index it for speed. Handle parsing on the server to avoid redundant performance costs. Maybe spin up the back-end with actix-web if you want to get autistic.

hahaha, actixweb, its for rust

I usually have data stored in ssd and use cat and grep to search quickly , it saves time

Arguably you're not wrong with the whole setup using ES, its just a pain parsing everything into a format you can actually ingest and search across.

(March 31, 2022, 04:21 AM)HaxonGhost Wrote:

(March 30, 2022, 07:01 PM)frydembrains Wrote: Throw it in a NoSQL database and index it for speed. Handle parsing on the server to avoid redundant performance costs. Maybe spin up the back-end with actix-web if you want to get autistic.

hahaha, actixweb, its for rust

No shit.