Infinte scroll vs pagination...which gives a better UX?? Oppinions plz..

depends on the targeted audience, but unlimited scrolling will eventually result in pagination or your audience might run out of memory

If you want the user to stay in the app or the site as long as possible, I would prefer an infinite scroll. (something what facebook and twitter does).

If you want the user to navigate from the app or the site as quickly as possible, I would prefer a paginated UX (something what google and bing does).

As darkmukke says it, it depends.
Great article about it “UX: Infinite Scrolling vs. Pagination” @101babich https://uxplanet.org/ux-infinite-sc...

I like infinite scroll but think pagination is the way depending on your app

Depends on the content, audience, and user base. Pagination is typically better for dealing with large sets of data where hunting occurs. This comes down to the way we hunt for information -- pagination clearly separates lists and typically doesn't involve any animation that may cause a user to lose their sense of orientation. Overall, the location of the first item in a list remains static between pages.

If you scan through a collection of, say, Tumblr posts in an infinite loading list, take note of where your eyes come to rest when you hit the last item. Then bring in the next set -- if you find it difficult to keep track of the spot, you're like most people! ...it tends to cause us to reorient ourselves with the start and end of a set of information. This works well when the task isn't critical or time-sensitive.

In the end, though, it really just depends.

Why not both? You can limit your cache so you won't have memory issues and re-request the data if needed. How? Load 20 items at a time, cache-max 40, once hitting the cache limit just dump the first 20 entries. Use virtual scroll to give the user a feeling he's positioned relative to the data viewed so far.