Talk:In-memory processing: Difference between revisions

Content deleted Content added
AlexHajnal (talk | contribs)
Article has multiple technical issues
Agreed. Until the rewrite happens, I think WP:STUBIFY is appropriate
Line 25:
 
This discussion hasn't really gone anywhere and the proposer is MIA, so I'm removing the merge proposal from the top of the article page. — [[user:MaxEnt|MaxEnt]] 18:58, 11 September 2015 (UTC)
 
==Rewrite==
 
From a technical standpoint this article has numerous issues. The article implies that by keeping all data in-memory no indexing is needed; this is incorrect for larger datasets. The reason for this is that a task's time complexity remains constant even if the underlying hardware (hard disk to RAM in the article) changes. In addition, the article implies that traditional databases hit disk for all queries and do not, e.g. cache data and indices in RAM. Additionally the article states that a traditional DB can only do one task (a write, a query, a view, etc.) at a time; this is not true. There are many other issues as well along with contradictions from paragraph to paragraph. Input from a DBA would be ideal but my opinion as a software architect/engineer is that the article should either be completely rewritten (preferably by a DBA) or deleted. — [[User:AlexHajnal|Alex Hajnal]] ([[User talk:AlexHajnal|talk]]) 07:02, 25 November 2015 (UTC)
 
:{{Ping|AlexHajnal}} Agreed. Until the rewrite happens, I think [[WP:STUBIFY]] is appropriate. -- [[user:intgr|intgr]]&nbsp;<small>[[user talk:intgr|[talk]]]</small> 08:23, 25 November 2015 (UTC)