rezarazmjoo / sparserss

Automatically exported from code.google.com/p/sparserss
Other
0 stars 0 forks source link

"Mark as read" works slowly #67

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
There is to much time needed to mark messages as read even if you have 1 
message in the rss feed. This delay doesn't depend on messages count.

Original issue reported on code.google.com by kaktus.c...@gmail.com on 27 Jun 2011 at 1:37

GoogleCodeExporter commented 9 years ago
Do you perform the action from the feed-overview or from the entry-overview of 
a certain feed?

Also, do you have the tabs enabled?

Original comment by handschuh.stefan on 27 Jun 2011 at 9:18

GoogleCodeExporter commented 9 years ago
I marked items from feed-overview.
There are some lags when i mark messages as read even all of the message 
already marked as read. 
Tabs? What do you mean? 

Original comment by kaktus.c...@gmail.com on 28 Jun 2011 at 5:59

GoogleCodeExporter commented 9 years ago
You can enable tabs in the settings but apparently you do not have them active.

What is your device (just the model)?

Original comment by handschuh.stefan on 6 Jul 2011 at 7:45

GoogleCodeExporter commented 9 years ago
LG optimus one P500

Original comment by kaktus.c...@gmail.com on 7 Jul 2011 at 5:05

GoogleCodeExporter commented 9 years ago
>You can enable tabs in the settings but apparently you do not have them active.
I have switched on tabs. But I use only Overview tab.

Original comment by kaktus.c...@gmail.com on 7 Jul 2011 at 5:09

GoogleCodeExporter commented 9 years ago
If you are only using the overview-tab, then you can also disable the tabs.

Unfortunately, I am still unable to reproduce this behavior even on the very 
slow emulator so it is no lack of performance but some other glitch.

Original comment by handschuh.stefan on 8 Jul 2011 at 8:19

GoogleCodeExporter commented 9 years ago
It usually takes about 2-4 seconds.

Original comment by kaktus.c...@gmail.com on 8 Jul 2011 at 9:29

GoogleCodeExporter commented 9 years ago
Ok, can you try the following:
 - unmount the sd card
 - add a feed
 - refresh
 - mark as read

Original comment by handschuh.stefan on 8 Jul 2011 at 9:33

GoogleCodeExporter commented 9 years ago
Probably your supposition is correct.
It works fine with internal phone memory.
Is possible to fix it?

Original comment by kaktus.c...@gmail.com on 8 Jul 2011 at 9:58

GoogleCodeExporter commented 9 years ago
Maybe the best way is to add an option to move the hole database to the 
telephone storage.

Original comment by handschuh.stefan on 8 Jul 2011 at 12:31

GoogleCodeExporter commented 9 years ago
Ok, I fixed this in revision 141, but in order to use this in the next version, 
you have to create a file named "ignore" (no file extension) and place it in 
the sparserss folder of your SD card.

Original comment by handschuh.stefan on 8 Jul 2011 at 12:39

GoogleCodeExporter commented 9 years ago
It's strange. SD works enough fast. I have sd class 4.
I have some experience in java. But i don't ever write for android.
Can it be a architecture problem?

Original comment by kaktus.c...@gmail.com on 8 Jul 2011 at 1:25

GoogleCodeExporter commented 9 years ago
I think this workaround is not best decision. Could you have a look once more?

Original comment by kaktus.c...@gmail.com on 8 Jul 2011 at 1:41

GoogleCodeExporter commented 9 years ago
Well, the actual workaround is only in the sourcecode and not yet in a package. 
So unless you have compiled the program by yourself, this issue is still not 
fixed on you phone.

The above procedure (unmount sd card ...) was just to verify the cause of the 
lag.

I could only make a rough guess about the problem with the slow sd-card.

Original comment by handschuh.stefan on 8 Jul 2011 at 1:46

GoogleCodeExporter commented 9 years ago
Hi there,
I have that issue too.

With some tests, here is what happens :
- Open a certain feed; there are ~50 articles and 3 unread entries. "Make as 
read" action takes about 4 secs.

- Open "All" tab; there are ~150 articles and 3 unread entries. "Make as read" 
action takes same time, ~4secs.

- On the overview tab (main tab); there are 3 unread entries for all feeds 
(~150 articles). "Mark all as read" action takes no time, it's immediate.
(that last test with 50 unread articles : same, immediate)

I have a classe 6 sd card.

To set all as read, I think re-read the all entries database to find those 
which are not read, or something like that right ?
I notice that bigger the feed is, longer the time is to set all as read.

If I had a feed with only 10 entries, go in the overview of that feed, and mark 
as read, it's immediate.

I don't know if this can help you...

Original comment by Rodrigue...@gmail.com on 12 Jul 2011 at 12:42

GoogleCodeExporter commented 9 years ago
Please try to add necessary indexes to table entries.

Original comment by kaktus.c...@gmail.com on 12 Jul 2011 at 1:37

GoogleCodeExporter commented 9 years ago
Adding an index would not help to much in that case.

As described in comment 15, the mark-as read performance is good if the entries 
are not shown. Can you confirm that?

Original comment by handschuh.stefan on 12 Jul 2011 at 2:12

GoogleCodeExporter commented 9 years ago
>> As described in comment 15, the mark-as read performance is good if the 
entries are not shown. Can you confirm that?
I confirm that.

Original comment by kaktus.c...@gmail.com on 13 Jul 2011 at 5:10

GoogleCodeExporter commented 9 years ago
In revision 147 and revision 148, I changed the view to an asynchronous one 
which means that it becomes unsynchronized with the data set at a certain point 
but only until the "mark as read"-query is finished.

This should fix this issue since the ui does not wait for the database any more.

Original comment by handschuh.stefan on 15 Jul 2011 at 8:17

GoogleCodeExporter commented 9 years ago
Version 0.9.3 is now in the market and in the Downloads section.

Original comment by handschuh.stefan on 15 Jul 2011 at 8:43

GoogleCodeExporter commented 9 years ago
It works properly now. Thank you.

Original comment by kaktus.c...@gmail.com on 18 Jul 2011 at 4:49