Re: RFR: 8317698: Optimization for URLEncoder

2023-10-09 Thread Claes Redestad
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-09 Thread 温绍锦
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-09 Thread Claes Redestad
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-09 Thread 温绍锦
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-09 Thread Claes Redestad
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-08 Thread 温绍锦
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-08 Thread Claes Redestad
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-08 Thread Claes Redestad
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo

Re: RFR: 8317698: Optimization for URLEncoder

2023-10-07 Thread Jie Fu
On Fri, 6 Oct 2023 20:55:40 GMT, 温绍锦 wrote: > @cl4es and @Glavo have already made some very good optimizations to > URLEncoder, but we can continue to improve. > > The current URLEncoder's Predicate for DONT_NEED_ENCODING is based on BitSet, > which is actually a table lookup. The actual perfo