Eps going to 48 hour stats reporting

[emeleel]

I just found this on my profile page:

Sitewide: (February 13, 5:45 pm PDT) Beginning February 13 visits to reviews will be posted to members accounts in a 48hr time frame instead of a 24hr period. Visits from February 13th will be posted on February 15th, and so on.

Thoughts?

[magenta321]

I don't watch my stats like I used to, since we don't get money for each click.

I really don't care, especially if they are doing to save money (which seems to be the only reason they would do this).

[Grouch]

*sigh*
oh the days when it was real-time updates.
dem were da days, dem were da days.....

(circa Jurassic Era)

[jkkelley]

Originally posted by emeleel
Thoughts?

Just one more reason to put less effort and interest into reading, writing and rating.

There's no money to write for; there is only recognition, as expressed in reads, hits, comments. So, having taken away all the money, the next logical place to chip away is at factors that convey recognition.

And for what savings to the company? Can't be too much.

I'm too disgusted to speak further of this in this forum, at this particular moment, in ways compliant with the rules thereof.

jkk

[Joubert[$]]

Originally posted by jkkelley



And for what savings to the company? Can't be too much.

The only thing I can think of is that the job now takes too long or consumes too many resources to run faithfully at night. I suspect that's why the move from real-time occurred. I loved watching hits go up in the hour or two after posting too, but I know what that kind of real-time work does to my company's web site.

Joubert: Hey, on log-in, we could do X and Y and, check out this Z idea.

CTO: Yes, we could. But the sun will explode. Okay, the sun won't explode. But you're adding a minimum of 10 seconds to the log-in process. Can't do it.

Joubert: But it's cool. Rewrite the programs, buy more computers, let's make it happen.

CTO: Fine. But it's 6 months and there's no more development unless we add staff, which will cut income. How much are you willing to pay for these?

Joubert: I don't want to pay for it. I just want it to happen.

CTO: Let me know when you're willing to fund it.

-------

At the risk of publicly defending the decision - always a risk when people's passions flare - I'm guessing a similar conversation has happened at Epinons. So it's a two day cycle -- we'll live. And if you check your Epinions every morning, you can post extra here on the off-mornings.

[lynnzop[$]]

Okay,

#1, I don't care because of the reasons Margaret already stated
#2, I'm not a computer genius, but HELLO...batch (in my world) takes longer and clogs up the pipes more than real-time. No savings IMO



Maybe just being dumb blonde.

Lynn

[Joubert[$]]

Originally posted by lynnzop
Okay,

#1, I don't care because of the reasons Margaret already stated
#2, I'm not a computer genius, but HELLO...batch (in my world) takes longer and clogs up the pipes more than real-time. No savings IMO



Maybe just being dumb blonde.

Lynn

Not dumb, Lynn, but we do a lot of database work, and unfortunately, some jobs get too big to run without slowing everything to a crawl, or worse, simply hang when there's too much to process.

Without having knowledge of the systems, the program code and all the rest, I really can't comment so I was using my company's experiences.

One more true war story. I manually created the coolest query in the world. Our CEO actually had me bind the results so he could show it to the Board as an example of what we were doing for the future.

The programming team attempted to automate my week's worth of manual work. Everyone buzzed about and began planning for how we could use the new data.

Small tests ran fine (batches, if you will, of cities) so we ran a global report. We kicked off the job at night and watched the network's resource die. We finally reprioritized the job the next morning and killed it altogether the next afternoon. Our calculation was that this nifty report would take 4 days to run.

Yeah, we later changed some stuff, dropped hundreds of thousands on dedicated boxes, changed some code, migrated the data to Oracle and got it to run. That was muy expensive.

[susanwhipple]

I stopped caring about updates when it went to daily. I get ratings notifications on all my posts. I get more information from the email + the date rated + the sort by date then I ever did with real time updates.
And I have to say (I hope I don't jinx it) that email alerts have been quite dependable in the past 6 months.

[frazzledspice]

I wasn't even aware how frequently updates were occurring, so every 48 hours is fine with me.

[Joubert[$]]

Well, today's actions strike me as a clear sign that Epinions is listening to the site's most active members. Here's the status message that appears now:

Sitewide: (February 14, 4:00 pm PDT) A Feb. 13th site status message announced that visits-to-reviews updates would move to a 48-hour cycle. We made this change to accommodate a new back-end system designed to make tracking more reliable. Member feedback indicated the importance of daily updates. As a result, we have optimized the new system in favor of 24-hour updates, at the cost of regular morning updates. Future updates will occur a few hours later in the day. Effective Feb. 14th, 24-hour updates will be posted in the early afternoon rather than the morning. Thanks for your understanding during this transition.

[amykhar]

:thumbs:

[Grouch]

When E.A. Hutton speaks.....Nirav listens.