Re: dequeueReusableCellWithIdentifier bad performance in case of less number of cells?

What is the string you are using for the identifier? All the code I have seen from India that I have seen (from maybe 5 different developers) using a cell identifier - for SOME REASON - makes the identifier for each cell a different value. Are you using one value for the identifier or is it a

Re: dequeueReusableCellWithIdentifier bad performance in case of less number of cells?

> On Jan 10, 2018, at 3:48 AM, Devarshi Kulshreshtha > wrote: > > I had a discussion with my colleagues regarding use > of dequeueReusableCellWithIdentifier, few of them are under assumption that > if there are less number of cells it is better to directly alloc

Re: dequeueReusableCellWithIdentifier bad performance in case of less number of cells?

Easiest way is to write both solutions and analyse them with Instruments. Best, ir > Am 10.01.2018 um 12:48 schrieb Devarshi Kulshreshtha > : > > I had a discussion with my colleagues regarding use > of dequeueReusableCellWithIdentifier, few of them are under

dequeueReusableCellWithIdentifier bad performance in case of less number of cells?

I had a discussion with my colleagues regarding use of dequeueReusableCellWithIdentifier, few of them are under assumption that if there are less number of cells it is better to directly alloc init a UITableViewCell in place of using dequeueReusableCellWithIdentifier. They are saying that since at