Looking down the road
| Project: | Fivestar |
| Version: | 6.x-1.19 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Sorry if I posted this a minute ago... looks like it didnt get saved.
I know this topic has been beat over the heead but stay with me.
I am curious about the long term viability of using the current multi-axis rating with cck and fivestar. Assume over 100,000 votes get accumulated... will taking this approach have any repercussions to system performance or anything?
When it comes time to upgrade to drupal 7 or 8 in the future and a new multi axis rating method has taken shape... will all these ratings have to be lost bc it was a temp fix and all users will have to start their ratings from scratch? Or will it be possible to conver them over with this current CCK approach...
The reason that I ask... this is the type of thing that will determine if a site is launched in a month or over a year. Thanks for any help.
#1
Fivestar (or more accurately MySQL) won't have a problem with anything less than multi-million registered votes. You could probably surpass 20 million votes with good dedicated hardware. More important is how *frequently* votes are registered, but that can be easily solved by generating vote totals on cron (an option in VotingAPI) instead of on vote.
Any votes registered through the CCK method will immediately work with the "official" multi-axis rating system in Flag 2.x, since both approaches save the votes in the same place. VotingAPI has had multi-axis support forever, it's just a matter of making it so that Fivestar registers these votes through its interface.