2016-02-22 22:04:42 +00:00
|
|
|
{
|
2019-09-12 12:38:16 +00:00
|
|
|
"name": "StatusIm-Mobile",
|
2016-02-22 22:04:42 +00:00
|
|
|
"version": "0.0.1",
|
|
|
|
|
"private": true,
|
|
|
|
|
"scripts": {
|
2019-08-06 16:16:51 +00:00
|
|
|
"start": "react-native start"
|
2016-02-22 22:04:42 +00:00
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2019-10-14 05:24:35 +00:00
|
|
|
"@react-native-community/netinfo": "^4.4.0",
|
2019-01-14 09:42:29 +00:00
|
|
|
"bignumber.js": "git+https://github.com/status-im/bignumber.js.git#v4.0.2-status",
|
2019-09-09 17:25:02 +00:00
|
|
|
"buffer": "^5.4.2",
|
2019-09-06 10:05:26 +00:00
|
|
|
"chance": "^1.1.0",
|
2019-10-03 10:07:14 +00:00
|
|
|
"create-react-class": "^15.6.2",
|
2019-09-06 10:05:26 +00:00
|
|
|
"emojilib": "^2.4.0",
|
|
|
|
|
"eth-phishing-detect": "^1.1.13",
|
Fix message ordering and improve performance rec. messages
This commit does a few things:
==== Ordering of messages ====
Change the ordering of messages from a mixture of timestamp/clock-value to use
only clock-value.
Datemarks are now not used for sorting anymore, which means that the
order of messages is always causally related (not the case before, as we
were breaking this property by sorting by datemark), but datemark
calculation is unreliable (a reply to a message might have a timestamp <
then the message that is replied to).
So for timestamp calculation we
naively group them ignoring "out-of-order timestamp" messages, although
there's much to improve.
It fixes an issue whereby the user would change their time and the
message will be displayed in the past, although it is still possible to
craft a message with a lower clock value and order it in the past
(there's no way we can prevent this to some extent, but there are ways
to mitigate, but outside the scope of this PR).
==== Performance of receiving messages ====
The app would freeze on pulling messages from a mailserver (100 or so).
This is due to the JS Thread being hogged by CPU calculation, coupled
with the fact that we always tried to process messages all in one go.
This strategy can't scale, and given x is big enough (200,300,1000) the
UI will freeze.
Instead, each message is now processed separately, and we leave a gap
between processing each message for the UI to respond to user input
(otherwise the app freezes again).
Pulling messages will be longer overall, but the app will be usuable
while this happen (albeit it might slow down).
Other strategies are possible (calculate off-db and do a big swap,
avoiding many re-renders etc), but this is the reccommended strategy by
re-frame author (Solving the CPU Hog problem), so sounds like a safe
base point.
The underlying data structure for holding messages was also changed, we
used an immutable Red and Black Tree, same as a sorted map for clojure, but we use
a js library as is twice as performing then clojure sorted map.
We also don't sort messages again each time we receive them O(nlogn), but we
insert them in order O(logn).
Other data structures considered but discarded:
1) Plain vector, but performance prepending/insertion in the middle
(both O(n)) were not great, as not really suited for these operations.
2) Linked list, appealing as append/prepend is O(1), while insertion is
O(n). This is probably acceptable as messages tend to come in order
(from the db, so adding N messages is O(n)), or the network (most of
them prepends, or close to the head), while mailserver would not follow this path.
An implementation of a linked list was built, which performed roughtly the
same as a clojure sorted-map (although faster append/prepend), but not
worth the complexity of having our own implementation.
3) Clojure sorted-map, probably the most versatile, performance were
acceptable, but nowhere near the javascript implementation we decided on
4) Priority map, much slower than a sorted map (twice as slow)
5) Mutable sorted map, js implementation, (bintrees), not explored this very much, but from
just a quick benchmark, performance were much worse that clojure
immutable sorted map
Given that each message is now processed separately, saving the chat /
messages is also debounced to avoid spamming status-go with network
requests. This is a temporary measure for now until that's done directly
in status-go, without having to ping-pong with status-react.
Next steps performance wise is to move stuff to status-go, parsing of
transit, validation, which is heavy, at which point we can re-consider
performance and how to handle messages.
Fixes also an issue with the last message in the chat, we were using the
last message in the chat list, which might not necessarely be the last
message the chat has seen, in case messages were not loaded and a more
recent message is the database (say you fetch historical messages for
1-to-1 A, you don't have any messages in 1-to-1 chat B loaded, you receive an
historical message for chat B, it sets it as last message).
Also use clj beans instead of js->clj for type conversion
Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
2019-10-24 14:23:20 +00:00
|
|
|
"functional-red-black-tree": "^1.0.1",
|
2019-09-13 22:01:39 +00:00
|
|
|
"hermes-engine": "0.2.1",
|
2019-09-06 10:05:26 +00:00
|
|
|
"hi-base32": "^0.5.0",
|
|
|
|
|
"i18n-js": "^3.3.0",
|
2019-08-29 10:47:39 +00:00
|
|
|
"qrcode": "^1.4.1",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react": "^16.8.6",
|
|
|
|
|
"react-dom": "^16.4.2",
|
|
|
|
|
"react-native": "^0.60.5",
|
2019-09-06 10:05:26 +00:00
|
|
|
"react-native-background-timer": "^2.1.1",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-native-camera": "^3.3.3",
|
2019-08-06 16:16:51 +00:00
|
|
|
"react-native-config": "git+https://github.com/status-im/react-native-config.git#0.11.2-1-status",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-native-dialogs": "^1.0.4",
|
|
|
|
|
"react-native-fetch-polyfill": "^1.1.2",
|
|
|
|
|
"react-native-fs": "^2.14.1",
|
2019-10-03 05:42:01 +00:00
|
|
|
"react-native-gesture-handler": "^1.3.0",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-native-image-crop-picker": "^0.25.0",
|
2019-01-18 11:07:55 +00:00
|
|
|
"react-native-image-resizer": "git+https://github.com/status-im/react-native-image-resizer.git#1.0.0-1-status",
|
2018-12-09 14:58:03 +00:00
|
|
|
"react-native-keychain": "git+https://github.com/status-im/react-native-keychain.git#v.3.0.0-status",
|
2019-02-02 17:21:05 +00:00
|
|
|
"react-native-languages": "^3.0.2",
|
2019-08-06 16:16:51 +00:00
|
|
|
"react-native-mail": "git+https://github.com/status-im/react-native-mail.git#v4.0.0-status",
|
2019-07-05 12:21:00 +00:00
|
|
|
"react-native-navigation-twopane": "git+https://github.com/status-im/react-native-navigation-twopane.git#v0.0.2-status",
|
2019-10-14 05:24:35 +00:00
|
|
|
"react-native-screens": "^1.0.0-alpha.23",
|
2019-05-07 06:37:43 +00:00
|
|
|
"react-native-shake": "^3.3.1",
|
2019-09-06 10:05:26 +00:00
|
|
|
"react-native-splash-screen": "^3.2.0",
|
2019-09-30 12:44:09 +00:00
|
|
|
"react-native-status-keycard": "^2.5.12",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-native-svg": "^9.8.4",
|
2019-05-30 14:01:20 +00:00
|
|
|
"react-native-touch-id": "^4.4.1",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-native-webview": "^6.11.1",
|
2019-08-06 16:16:51 +00:00
|
|
|
"react-native-webview-bridge": "git+https://github.com/status-im/react-native-webview-bridge.git#fix/community-webview",
|
2019-10-03 10:07:14 +00:00
|
|
|
"react-navigation": "^3.11.0",
|
2019-09-06 10:05:26 +00:00
|
|
|
"web3-utils": "^1.2.1"
|
2019-07-03 19:00:51 +00:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2019-08-06 14:00:51 +00:00
|
|
|
"@babel/generator": "7.0.0",
|
|
|
|
|
"@babel/helper-builder-react-jsx": "7.0.0",
|
|
|
|
|
"@babel/plugin-transform-block-scoping": "7.0.0",
|
|
|
|
|
"@babel/preset-env": "7.1.0",
|
|
|
|
|
"@babel/register": "7.0.0",
|
2019-07-03 19:00:51 +00:00
|
|
|
"coveralls": "^3.0.4",
|
2019-08-06 14:00:51 +00:00
|
|
|
"nyc": "^14.1.1",
|
2019-08-29 11:11:46 +00:00
|
|
|
"process": "0.11.10",
|
2019-08-06 14:00:51 +00:00
|
|
|
"rn-snoopy": "git+https://github.com/status-im/rn-snoopy.git#v2.0.2-status"
|
2016-02-22 22:04:42 +00:00
|
|
|
}
|
2016-07-22 08:53:12 +00:00
|
|
|
}
|
