User - Revision history

Kademlia: /* Storage System Design */

2020-04-27T15:31:29Z

Storage System Design

← Older revision		Revision as of 15:31, 27 April 2020
Line 2:		Line 2:

	=Storage System Design=		=Storage System Design=
	<br />		Userprofiles are generally split in to smaller parts. This helps with memory-management, load-times and in the end data-parsing within the backend.

			For example: If we store everything inside a user.json this could easily get up to 200kb+ per File. Scanning for homepoints in general in a given area would require to load 100.000* 0,2MB => 20GB of data.

			By splitting the data into chunks/containers we can decrease the filesize to probably <10kb per File. 100.000* 0,01MB => 1 GB. Factor 20 speed increase and this does not include better caching strategy by HDD/DB as most likely only a subset of the data will be queried regularly.<br />

	==UserOptions==		==UserOptions==
Line 51:		Line 55:
	</syntaxhighlight>		</syntaxhighlight>

	== UserPods ==		==UserPods==
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">
	Home (0, HomePod.class),		Home (0, HomePod.class),

Kademlia at 15:27, 27 April 2020

2020-04-27T15:27:02Z

← Older revision		Revision as of 15:27, 27 April 2020
Line 1:		Line 1:
	'''Storage system design needed.'''		'''Storage system design needed.'''

	= Storage System Design =		=Storage System Design=
	<br />		<br />

	== UserOptions ==		==UserOptions==
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">

Line 49:		Line 49:
	ShopDefaults (304, new ArrayList<String>()),		ShopDefaults (304, new ArrayList<String>()),
	ActiveAccount (305, AccountId.class), // Account		ActiveAccount (305, AccountId.class), // Account
			</syntaxhighlight>

			== UserPods ==
			<syntaxhighlight lang="java">
			Home (0, HomePod.class),
			Backpack (1, BackpackPod.class),
			Chat (2, ChatPod.class),


	</syntaxhighlight>		</syntaxhighlight>

Kademlia at 15:26, 27 April 2020

2020-04-27T15:26:20Z

@@ Line 1: / Line 1: @@
-Storage system design needed.
+'''Storage system design needed.'''
 We need to (possibly) store:
-* ModelProfile  -> ALWAYS LOADED
+*ModelProfile  -> ALWAYS LOADED
-* accounts -> ALWAYS LOADED
+*accounts -> ALWAYS LOADED
-* UserProfile -> loaded when online (?)
+*UserProfile -> loaded when online (?)
-* userstats profile -> loaded when online (?)
+*userstats profile -> loaded when online (?)
-* Mails (UUID <> MailProfile ?)
+*Mails (UUID <> MailProfile ?)
-* Homes (UUID <> MailProfile ?) vs stored in User (Component)
+*Homes (UUID <> MailProfile ?) vs stored in User (Component)
+*

Kademlia: Created page with "Storage system design needed. We need to (possibly) store: * ModelProfile -> ALWAYS LOADED * accounts -> ALWAYS LOADED * UserProfile -> loaded when online (?) * userstats..."

2020-03-29T21:24:13Z

Created page with "Storage system design needed. We need to (possibly) store: * ModelProfile -> ALWAYS LOADED * accounts -> ALWAYS LOADED * UserProfile -> loaded when online (?) * userstats..."

New page

Storage system design needed.

We need to (possibly) store:

* ModelProfile -> ALWAYS LOADED
* accounts -> ALWAYS LOADED
* UserProfile -> loaded when online (?)
* userstats profile -> loaded when online (?)
* Mails (UUID <> MailProfile ?)
* Homes (UUID <> MailProfile ?) vs stored in User (Component)
*