Timestamp delay/lag/cache issue continues

[daledoc1]

The 2 attached screen shots were taken only seconds apart just now (note the screenshot timestamps in the file names).

1. What was displayed to a forum GUEST (the timestamp for the post in question is "off" by ~36 hours).

2. What is "correctly" visible to LOGGED IN user (the timestamps for the post in question is correct).

{{The related problem of posts taking 3, 4 or 5 minutes or more to appear also persists -- it's hard to know if one's posts have actually been made, as they do not show up for a LONG time.}}

Thank you.

Edited April 25, 2016 by daledoc1
grammar typo

[Khadijah]

It's good you brought it up again @daledoc1 I noticed it has been realy bad, the pas few days even worse too. Only with constant refresh of the browser I could stay a bit up to the new posts, but even than sometimes it shows just now but in real already the delay is  6 or more minutes, and I'm really close to it in times. 

[John L. Galt]

And this is one of the reasons why I don't like having that little widget there in the first place.

[Khadijah]

30 minutes ago, John L. Galt said:

And this is one of the reasons why I don't like having that little widget there in the first place.

Yes but it's better than nothing at the moment 

[John L. Galt]

I prefer nothing.  I can look at the main forum page and see what has been replied to recently.  And I can make my own default stream to keep track of posts that I've already replied to.  The widget is a waste of space and a waste of resources, particularly since it doesn't filter out results that I don't need to see, such as the Malware removal forums, and constantly indexing such as that is taxing on server resources no matter how you look at it.

 

[Khadijah]

Yes for that matter I agree with you @John L. Galt, but for trackin fast the new created topics I can see it fast in a wink of my eye,  and don't need to scroll up and down the index, all the time 

just refresh end that tiny space of that widget.

But I have noticed there are time periods it is really bad (delay is up to 15 min. )  and time periods it is like the "normal" delay ( 6 min.) 

 

 

[John L. Galt]

Ahhh.  Now I can see why I dislike it so much.  My mouse is this one:  http://www.logitech.com/en-us/product/mx-master

It allows me to use the scroll wheel in 2 fashions - a click by click slow scroll, or as an unrestricted fly wheel, where the page scrolls as fast as I can get my mouse wheel to spin.  The original MX device and this one have a software-enabled feature that if you start to spin the wheel faster than a threshold that you specify, it automatically shifts from the click-to-click mode to the hyperscroll mode (flywheel).  And when I slow / stop the wheel it auto shifts back to the click-to-click modem.

So, that enables me to scroll from top to bottom in less than a second.  And even taking a full 2 seconds from top to bottom I can easily see where new topics are.

That is why I want this widget to be user configurable - for folks like you and DD1 that use it, you can enable it.  for folks like me who do not use it, we can hide it.

But, as always, IPS decides that they can make their board the  way the y see fit because they've been paid their money,

[Khadijah]

I can scroll from top to bottom  in two seconds if i want. @John L. Galt But You can have a mouse as fast as a rocket that brings you to the moon in 2 seconds but that will not solve the problems with the delay because that's not only a problem of that widget  I saw that even in an open topic on diferant posts and when I post it was not even right just when I had to refresh the time came in good again and I've seen for example in the past weekend a delay of 20 min. 

  

 

[John L. Galt]

You misunderstand.  I said that that is the reason I don't need the widget.  I can scroll through the main forum page in seconds and see what new topics there are, andwithout the buggy delay of the widget.

[Khadijah]

the buggy delay is not only in the widget, you misunderstood that 

[daledoc1]

Hi, @Khadijah and @John L. Galt:

I mean no disrespect, but this post is NOT about the "widget".

As my 2 screenshots in my original post, taken moments apart BEFORE and AFTER logging in show, I was trying to demonstrate inaccurate time stamps for the post times shown to "guests" vs. "users".  The screen shots do not relate to the widget.  All of this was > 36 HOURS after the post in question was made. So, this is not about widget delays....

I'm afraid your debate pro and con about the widget -- which I understand from previous threads was decided to be retained -- is quite a bit "off-topic", has been discussed elsewhere, and has muddied the water a bit for what I was trying to report, with no input at all yet from forum staff.

Thanks very much for your understanding,

[Khadijah]

I know it is not about the widget a I have seen it even in topics  @daledoc1 

[Khadijah]

 

Here is a screen shot to show when I just posted my previous post and the one of  daledoc1 was remain in my after posting on the same time that I open the topic what 

always surprises me, on every forum when you post the whole line of the topic refresh with your post imediatly you see my post is good "just now" so why does the post of 

daledoc1 stick on that 9 minutes ago as it was that I opened that time the topic? 

so after I refreshed I came out like this : 

 

And now you see  actually how all that post stay frozen in the topic and the delay here is 5 minutes  

 

Edited April 25, 2016 by Khadijah

[daledoc1]

No, your screenshots are something different, @Khadijah.

I'm sorry.

I know you are trying to help, but it is muddying the water.

I was reporting something that had been posted 36 HOURS EARLIER, that displayed differently at the exact same moment to a GUEST and to a LOGGED-IN USER.

The several minutes' delay in new posts appearing, as I mentioned in the "{{ }}" at the end of my original post, is related, but it is not the same problem.

As the OP in this thread, I respectfully ask that we please try to stay on-topic.

Thank you.

[Khadijah]

Well, maybe the moderator can split my part in a new topic than, for my part and so your issue wil stay clean, sorry that @daledoc1

 

[John L. Galt]

@DaleDoc1 - curious question.  You seem to bring up issues that show when being logged out versus being logged in.

IN this particular case, did you log out at around the time that the logged out screenshot shows?

When you opened your browser again, did you perform a CTRL + F5 to hard refresh the page (which ignores the cache and loads the page fresh from the website)?

I've tried to reproduce your error using 2 different browsers and I haven't seen times more different than a couple of minutes.  That makes me wonder if it is a cache loaded page instead of a live loaded page.

[daledoc1]

Hi:

8 minutes ago, John L. Galt said:

@DaleDoc1 - curious question.  You seem to bring up issues that show when being logged out versus being logged in.

IN this particular case, did you log out at around the time that the logged out screenshot shows?

When you opened your browser again, did you perform a CTRL + F5 to hard refresh the page (which ignores the cache and loads the page fresh from the website)?

I've tried to reproduce your error using 2 different browsers and I haven't seen times more different than a couple of minutes.  That makes me wonder if it is a cache loaded page instead of a live loaded page.

I'm glad it works for you.

The problem is real, at least for me.  I suspect I am not alone, but others do not notice or do not report.

Hard refreshing has no impact. New browser sessions have no impact (and I clear all data when I close a session). This was not the only time I have observed this behavior.

I am not a computer engineer. I can only report and document -- as best I can -- the behavior I observe.

Something seems to be caching somewhere somehow, but I lack the expertise to explain or resolve it.
And, alas, I don't have hours and hours of time for complex troubleshooting.
As a guest, the post in question had a time stamp 36 hours "old". As soon as I logged in, the correct time stamp was visible. The only difference was being here as a guest vs. logging in.  I don't know how else to explain it.

It does not affect ALL posts.

>>I am NOT talking about the delay in post appearance OR the discrepancy between post time-stamps in one  forum section vs. the widget.<<
>> It may or may not be related to these other issues.<<

It is a new problem with the new IPS software and it is unique to this forum.
That's all I can say.

Perhaps a forum staff member will be able to provide more insight.

Otherwise, perhaps they will please just amicably close this thread, so that we don't waste more time here.

Thank you,

[noknojon]

@ DD1              

Stop and think that I am on the other side of the world (time-wise) and many of my time-stamps are totally out of sync with what you see and read.
I waited till 9.00AM to report that my internet was on and off at strange times. My report was @ 10.00AM Monday by the time they rang back (a service so you are not sitting on the phone for hours) and the "South African" operator that reset my internet was in the middle of his shift at almost midnight Sunday his local time.

So I was reporting a problem 10 hours prior to his reaching there.. You will find this on any International forum, where your time stamp and their time stamp can change in a series of posts. This was always one of the comments I had from Bleep Comp Forum when I was helping people there. They would ask if their time needed resetting.

I do not know what time this will report up to when I hit Submit Reply. It may show yesterday, or it may hit tomorrows date. Just one of those things with international forums, and you may reply yesterday, or the board may compensate for this. I just posted a "Jokes" item many hours prior to the date being valid ??

Since this version has no Preview abilities, I just let it lay at whatever time / date it lands -

EDIT - I may add that Guest View seems to be HIS local posted time while Logged In showed YOUR local time.
Nothing wrong there ..

Edited April 26, 2016 by noknojon

[AdvancedSetup]

Topic closed per user request