|
|
Posted by R. Rajesh Jeba Anbiah on 10/11/27 11:39
NC wrote:
> ReGenesis0@aol.com wrote:
> >
> > I guess, I must ask again- is there an elegant way to teack 'just
> > the hits in the last week,' essentiallg dropping the 'back-end' hits
> > as they elapse past the hit-time, WITHOUT keeping an individual
> > record of all hits over the course of the week?
>
> You could try daily totals... Say, you have a MySQL table called hits:
<snip Nikolai Chuvakhin's MySQL solution>
Say, for example, take a product search engine and it's core DB
table:
products: id, name, hits
If the 'products' table is updated with hits count lively, it might
affect performance; but certainly to rank the products we need such
table structure. I don't have any idea, how it's done in some high
traffic sites.
But, when I last time dig on this subject, I read somewhere (or
mistakenly understood) that such sites don't rely on DB. The product
data is stored in filesystem with hash like system:
c:\products\01\product1.data
\02\product2.data
And it's been "indexed"--not sure, how it's indexed. The same
technique is used by search engines(?). If anyone has any good
experience on this topic, kindly share the architecture. I'm much
curious.
--
<?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com Blog: http://rajeshanbiah.blogspot.com/
Navigation:
[Reply to this message]
|