Hi Yogesh. I have no experience of uploading to Sharepoint, but fundamentally I don't currently see any particular issues with the size of your DB even allowing for the kind of growth which is normal with Access. Its internal performance is not directly related to the size of the MDB file holding the Access application itself.
For applications accessed via web-based pages or similar it would be more usual to deploy a true client-server back-end database (based on SQL Server or similar) even if Access was used as the front end application. The issues you raise would not really apply in those circumstances at all.
Access applications can grow to around 4 to 5 times their 'optimal' size over time, hence the provision of the 'compact' part of the 'compact and repair' option under the Tools, Database Utilities menu in pre-2007 versions of Access. I doubt that this will of itself be much of an issue for you, though, at least not in terms of performance, but time will tell.
I would also advise, if you have not already done so, splitting the database into a front end which provides any forms, reports, queries and so on, and a back-end which just contains the tables. We have a basic article on what this entails in our Insights section under the title
Front-End / Back-End (FE/BE).
-Stewart