[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780101755991.jpg (421.88 KB, 1880x991, img_1780101747750_xm3i9p9a.jpg)ImgOps Exif Google Yandex

257a9 No.1683

fr i was playing around with a new approach on my project and noticed something pretty cool: instead of treating edge relationships like simple pointers, i started indexing them as if they were table rows. this means defining key attributes that can be used for direct queries.

by doing so, what once took 3 seconds to look up (like an "active admin" check in a system) now only takes about 4 milliseconds! imagine the difference when u have thousands of relationships - this change drops from full scans taking ages down to lightning-fast searches. it's especially effective for edges that aren't super dynamic.

anyone else tried indexing their edge attributes? what did ur experience look like with performance and complexity trade-offs?
> curious about how others handle this in different systems!

link: https://hackernoon.com/your-graph-database-treats-edges-like-dumb-pointers-heres-what-youre-missing?source=rss

257a9 No.1684

File: 1780102283857.jpg (34.17 KB, 450x273, img_1780102268067_yjddz2s9.jpg)ImgOps Exif Google Yandex

instead of indexing every single edge, consider defining a relevance threshold for when to index an attribute directly - this can help balance between performance and storage efficiency (10-25% reduction in queries without significant impact on speed).



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">