-
Notifications
You must be signed in to change notification settings - Fork 4
Performance_en
Flantter can change the startup speed and memory usage depending on the setting. Below are tips about these settings.
By turning it on, the startup process will be lighter, but the timeline will not be updated.
By turning it off, memory usage and startup time can be shortened. It is also possible to reduce memory usage by adjusting the size of the image.
You can specify the animation at the time of streaming connection.
-
ScrollToTop- Move to the latest tweet while scrolling. The most action is heavy. -
Expand- Shows an animation that expands when the tweet is inserted at the beginning. The operation is relatively light. -
Slide- Show the animation sliding from the side when the tweet is inserted at the beginning. The operation is relatively light. -
None- There is no animation. Therefore, the operation is lightest.
It seems good to set it to None or Slide etc. when feeling the heavy motion.
By enabling the DB it is possible to restore the timeline at startup, There is a possibility that the operation may be slightly heavy at the time of startup and tweet reception.
By turning off, you can reduce the startup time and memory usage.
You can specify how many tweets to save as data. The more storage you use, the more storage you use, the slightly heavier the operation.
At the time of startup, I will restore the previous tweets, but the startup time will be slightly slower. By turning it off you can speed up the boot time.
By turning it on, the startup process will be lighter, but the timeline will not be updated.
Increasing the number of accounts will increase startup time and memory usage proportionally. For accounts that you rarely use, you can reduce the weight by erasing the data.
The more columns you have, the more memory you use. Columns that you do not see against can be made lighter by deleting columns.
You can disable startup updates for each column. Startup processing will be slightly lighter.
You can set the number of tweets to be acquired during the update. The more updates, the more time for update processing, the more communication fees will be increased. 50-100 is the recommended value.
Although you can exclude unnecessary tweets etc. by using it, the operation at tweet reception becomes slightly heavier.
Setting it to () will make the most effective operation.