Vous pouvez ajouter des informations de localisation à vos Tweets, comme votre ville ou votre localisation précise, depuis le Web et via des applications tierces. Vous avez toujours la possibilité de supprimer l'historique de localisation de vos Tweets. En savoir plus
A while back I posted about working on a graph with a lot of nodes slow for runtime navigation. That work is now near complete (I've been doing and supporting other things I promise!) Some interesting (to me at least) stats follow.
Original graph of 625k assets: 642k nodes 1.8m edges Optimized graph: 353k nodes 615k edges File Size: 10.5 mb Of our 625k assets 405k are under 2k in size and are represented by ~200k nodes. We combine most of those into 30k "bundles" of assets.
In both cases it has 17k roots, and leafs are 75% of the nodes and takes about 5s to build. We currently build it single threaded (though some metadata related things happen multi-threaded) We can currently visualize the graph per root. After that our graph UI chokes @ 50k nodes
Due to some current restrictions we have to leave the 198k nodes of bundled assets in the graph. I will definitely be looking to change that in the future. Doing so would drop us to a ~7mb graph with 216k nodes and 424k edges.
I am well aware we have too many assets especially small ones. An unfortunate side effect of a pipeline that supports them well and us not being diligent previously about avoiding it.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.
